> There's definitely things they tried to improve on that... weren't really improvements. The way "assemblies" are matched in .NET is much more sophisticated- the goal there was to try to kill DLL hell. It evolved into the Global Assembly Cache, which is sort of the Windows Registry of DLLs. Not a huge fan of those bits.
The Global Assembly Cache did not make the jump to the modern .NET (Core). There was the thing called `dotnet store`, but it’s broken since .NET 6: https://github.com/dotnet/sdk/issues/24752
The assembly redirection hell has also been greatly reduced there.
In Swift was always going to be part of the OS (2022)dotnet
sdk
C#2020–2026
dotnet / sdk
sdk
Core functionality needed to create .NET Core projects, that is shared between Visual Studio and CLI
46Distinct people
61Mentions
1Explicit recommenders
3.2KGitHub stars
What to know before exploring
What it is
Core functionality needed to create .NET Core projects, that is shared between Visual Studio and CLI
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
https://github.com/dotnet/sdk/issues/6145 My favorite part is when someone figures out "telemetry" includes the MAC address, and the dev team just goes completely silent.
craftinator used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- dotnet/runtime · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:02:05 AM 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 year61 dated mentions
Observed mentions: 2020-05-21 14:25:34 UTC to 2026-07-27 09:32:34 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 30 | 4 | 26 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 7 | 1 | 6 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 4 | 0 | 4 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Welcome to dotnet sdk
This repository contains core functionality needed to create .NET projects that are shared between Visual Studio and the .NET CLI.
MSBuild tasks are under /src/Tasks/Microsoft.NET.Build.Tasks/.
See dotnet/project-system for the project system work that is specific to Visual Studio.
See the dotnetup documentation
for work on the .NET toolchain manager. Dotnetup changes should target the
release/dnup branch rather than main.
Common project and item templates are found in template_feed.
Build status
Visibility
All jobs
Public
Microsoft Internal
Installing the SDK
You can download the .NET SDK as either an installer (MSI, PKG) or a zip (zip, tar.gz). The .NET SDK contains both the .NET runtime and CLI tools.
Official builds
.NET SDK latest builds table
Looking for dotnet-install sources?
Sources for dotnet-install.sh and dotnet-install.ps1 are in the install-scripts repo.
How do I engage and contribute?
We welcome you to try things out, file issues, make feature requests and join us in design conversations. Be sure to check out our project documentation
This project has adopted the .NET Foundation Code of Conduct to clarify expected behavior in our community.
How do I build the SDK?
Start with the Developer Guide.
How do I test an SDK I have built?
To test your locally built SDK, run eng\dogfood.cmd after building. That script starts a new Powershell with the environment configured to redirect SDK resolution to your build.
From that shell your SDK is available in:
any Visual Studio instance launched via & devenv.exe
dotnet build
msbuild
How do I determine the timeline I must follow to get my changes in for a specific version of .NET?
Please see the Pull Request Timeline Guide.
How we triage and review PRs
With the SDK repository being the home for many different areas, we've started trying to label incoming issues for the area they are related to using Area- labels. Then we rely on the codeowners to manage and triages issues in their areas. Feel free to contact the owners listed in that file if you're not getting a response on a particular issue or PR. Please try to label new issues as that'll help us route them faster.
For issues related to the central SDK team, typically they are assigned out to a team member in the first half of each week. Then each member is asked to review and mark those needing further discussion as "needs team triage" and otherwise setting a milestone for the issue. Backlog means we will consider it in the future if there is more feedback. Discussion means we have asked for more information from the filer. All other milestones indicate our best estimate for when a fix will be targeted for noting that not all issues will get fixed. If you are not getting a quick response on an issue assigned to a team member, please ping them.
The example query used for triage of .NET SDK issues can be viewed here
For PRs, we assign a reviewer once a week on Wednesday, looking only at PRs that are green in the build. If you are contributing:
Get the PR green.
Include a test if possible.
Mention @dotnet-cli if you want to raise visibility of the PR.
License
The .NET SDK project uses the MIT license.
The LICENSE.txt and ThirdPartyNotices.txt in any downloaded archives are authoritative.
Read the full README on GitHubWhat Hacker News says
7 sourcesI do the same.
I have a small write-up here: https://chrlschn.dev/blog/2023/10/end-to-end-type-safety-wit...
You get end-to-end type safety (even better once you connect it to EF Core since you get it all ways to your DB).
With this setup with hot-reload (currently broken in .NET 8 [0]), productivity is really, really good. Like tRPC but with one of the most powerful ORMs out there right now.
[0] https://github.com/dotnet/sdk/issues/36918
In .NET BlazorYou're thinking of https://github.com/dotnet/sdk/issues/22247
In .NET 8That's a twisted and wrong narrative
"Unity like" refers to a Editor driven approach, not to a language
Unity became popular with its moonscript language (javascript like), they then ditched it to focus on C#, but what propelled unity to what it is today is the Editor driven approach, not c#, not DOTS (most AAA companies still fall back to lua in unity https://github.com/Tencent/xLua)
They are forced to transpile C# to C++ via IL2CPP as a result to target consoles/mobiles
C# is a disease when it comes to console/mobile support
It's a substantial dependency, quite heavy
And you are not free of unity like fuck ups, it's a microsoft language after all:
https://github.com/dotnet/sdk/issues/22247
And let's not forget when they changed the license of their debugger overnight to prevent people from using it in their products (jetbrains for examp
Read the rest
le)
And them deprecating open source tooling to a proprietary/closed one for vscode (c# devkit)
Let's be careful, and let's not recommend evil as an alternative to evil ;)
Another difference you might be surprised by is that the .NET tooling by default collects various data from your system and sends it to Microsoft [1].
If you want to avoid this (and still want to use .NET) you'll have to make sure that the environment variable DOTNET_CLI_TELEMETRY_OPTOUT is set to 1 in all contexts before touching anything.
[1] https://github.com/dotnet/sdk/issues/6145
In Writing Python like it's Rust> little to no impact to your risk exposure by having them collect anonymized telemetry
The key word there is "anonymized". What is the risk of the collected data accidentally being less anonymous than intended? What is the risk of accidentally collecting more data than intended? Microsoft has already had both types of accident [1][2], so I think it's fair to assume a risk close to 100% over time.
Even if users opt out, what is the risk of the opt-out mechanism at some point containing a bug that causes it to fail? Or the risk of the user at some point failing to properly configure the opt-out mechanism?
Is the company going to put as much effort into minimizing these risks as the end user would like? Is anonymization of telemetry going to be the top priority for the company?
[1] https://github.com/dotnet/sdk/issues/6145#issuecomment-2201
Read the rest
“Hot Reload removed from dotnet watch – Why?” (2021)
3 points · Open discussion