HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dotnet
AspNetCore.Docs
C#2017–2025
dotnet / AspNetCore.Docs

AspNetCore.Docs

Documentation for ASP.NET Core

11Distinct people
11Mentions
0Explicit recommenders
13.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Documentation for ASP.NET Core

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year11 dated mentions

Observed mentions: 2017-02-09 20:23:27 UTC to 2025-07-12 11:46:32 UTC.

01232017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC312
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

11 sources
Certain parts of Microsoft Learn are permissive, most .NET/C# documentation is Creative Commons Attribution: * Conceptual docs: https://github.com/dotnet/docs * BCL: https://github.com/dotnet/dotnet-api-docs * ASP.NET Core: https://github.com/dotnet/AspNetCore.Docs * WinForms/WPF: https://github.com/dotnet/docs-desktop The C# language specification is unfortunately a bit fuzzier, but the conceptual docs above include what most people want: https://github.com/dotnet/csharplang/discussions/4855 The updated unified C# language specification is CC, but it's still catching up to modern C#: https://github.com/dotnet/csharpstandard
In DevDocs
Their offical "SPA API Auth" involves paying for a third party OAuth server (called Duende IdentityServer, the ASP.NET Core built-in auth solution on the other hand is called ASP.NET Core Identity) and Microsoft refused to ship their own server because that would be "competing with the open source community" (there are multiple long Github threads on this which Microsoft product people would lock and mute). I wonder which PM got kickbacks for that decision. Originally Duende IdentityServer was free under Apache, and then they immediately turned into a paid solution after they became the "official" solution for API Auth. Microsoft also claims that standard cookie auth cannot be used for API Auth in a SPA scenario (their security engineers insist that you use JWTs), if you look through their Github issue threads, the ASP.NET Core engineers
Read the rest
seem to believe that the default ASP.NET Core Identity generic cookie auth is for MVC only and it is "not recommended" for use with SPAs. https://docs.microsoft.com/en-us/aspnet/core/security/authen... https://duendesoftware.com/products/identityserver They like to hide their dirty laundry behind clever developer advocacy teams and drowning it in Github bureaucracy but here are some examples: https://github.com/dotnet/AspNetCore.Docs/issues/25832 https://github.com/dotnet/AspNetCore.Docs/issues/7644#issuec... https://github.com/dotnet/AspNetCore.Docs/issues/24157 https://github.com/dotnet/AspNetCore.Docs/issues/18524 Their PMs are not building an open source product in good faith. As far as they are concerned, ASP.NET Core primarily exists as a funnel to send customers into Azure or buy stuff from Microsoft partner companies. Imagine if Vercel one day removes the standalone server hosting option and requires you to pay for their serverless cloud to use important features. This is what Microsoft is doing here right now with ASP.NET Core. If you lock your stack into their ecosystem, then be prepared to spend money either on redundant cloud subscriptions or developers reinventing the wheel on core features
In Thoughts on C# and .NET
If you’re just looking to be unblocked, use the Web SDK because you’re building and running combined web + hosted services [1]. The section linked shows the precise difference between the Web and Worker SDKs for hosted services. If you’re looking for docs on what all the SDKs are/do, and their source code, start here [2]. If you’re looking to just add the asp net core packages/apis to your basic sdk/console project, here [3]. But note that your app build/publish probably won’t work 100% because msbuild won’t be configured to do so. If you want to fix that manually (i.e do what the Web SDK does automatically), You can use the Web SDK props file as a starting point [4]. (Linked to in [2]) It seems well documented to me, but you’re welcome to propose new docs to the aspnet docs team. They’re very responsive [5]. [1] https://docs.microsoft.co
Read the rest
In .NET Myths Dispelled
Sure, but... I suggest that it is a trade off in which functionality is exchanged for convention and simplicity...and perhaps not for good reasons, or in a way that encourages good outcomes by default. If I was under the impression the ASP.NET team was on the ball and agreed with the decision they were making, I'd be more prepared to run with it... but I'm not. For example, there's an open github issue discussing the concerns people have raised about the ASP.NET team suggesting that razor pages are better than MVC. Read it yourself and you'll be extremely familiar with the various opinions on the matter: https://github.com/aspnet/Docs/issues/6146 This, is again, as I said before, an example of not everything that (specifically the ASP.NET team) does, being a good idea.
In Bing.com now runs on .NET Core
You can use the schema to figure out the valid values and descriptions for some of the values, so that might help. I agree that a technical reference would probably help since reading the schema isn't fun. Doesn't shock me that it's mostly GitHub search since most of our docs are hosted on GH: https://github.com/aspnet/Docs https://github.com/dotnet/docs You can always add a request to the docs UserVoice: https://msdocs.uservoice.com/forums/364242-general-site-feed... Azure also has its own docs UserVoice: https://feedback.azure.com/forums/217534-documentation
In Microsoft Docs – Unified technical documentation

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.