But Python itself is controlled by an independent foundation[1] and an elected steering council[2], which is very different from being owned by Microsoft.
For example, if Microsoft wanted to change CPython to automatically collect sloppily anonymized user data and send it to Microsoft without asking, as they did with .NET[3], I would expect the steering council reject that proposal.
[1] https://www.python.org/psf/
[2] https://peps.python.org/pep-0013/
[3] https://github.com/dotnet/sdk/issues/6145
In Web automation: Don't use Selenium, use Playwrightdotnet
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:56:20 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
8 sourcesWhat I personally find more egregious are dotfiles and dot-dirs on Windows, created by half-baked ports of Unix-first software (such as `ssh`).
Windows has `%APPDATA%` and `%LOCALAPPDATA%` that are accessible with `ShGetKnownFolderPath`[0], using the appropriate `KNOWNFOLDERID`[1]; all programs should put their configuration and cache data in these paths.
Windows also doesn't know what the dot at the beginning of a file/folder means. Instead, it and NTFS have something that's arguably better: a hidden file attribute `FILE_ATTRIBUTE_HIDDEN`[2], that's again settable/gettable when a file/directory is created or polled, rather than regex-ing for a full-stop.
The worst irony is Microsoft software creating dot-files and dot-dirs on Windows[3][4][5].
[0]: https://learn.microsoft.com/en-us/windows/win32/api/shlobj_c...
[1]: https://learn.microso
Read the rest
Are you sure about that? Can you share the steps I can run to reproduce that?
I am looking at the sources at https://packages.ubuntu.com/source/jammy-updates/dotnet6 and (as far as I can tell) they are applying a patch called 1500sdk-telemetry-optout.patch (originally from Fedora https://src.fedoraproject.org/rpms/dotnet3.1/blob/f36/f/cli-...) that is supposed to make telemetry opt-in.
There's a better fix landing upstream for .NET 7: https://github.com/dotnet/sdk/pull/25935
In .NET 6 is now in Ubuntu 22.04Just skimming the diff it looks like it was proper hot reloading.
https://github.com/dotnet/sdk/pull/22262/files
In .NET 6 is now in Ubuntu 22.04Does Godot's implenetation of C#/.net include the .net temeletry?
https://github.com/dotnet/sdk/issues/14556
In Godot 4.0 development enters feature freeze ahead of the first betaIf 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
This is a little out of date; the .NET single-file situation is pretty good as of .NET 5 (which came out in 2020).
These days, if you publish a single-file app all .NET libraries live in the executable and do not need to be unpacked at runtime. Native libraries still need to get unpacked at runtime (if your application uses any; many don't), but you just set the IncludeNativeLibrariesForSelfExtract build property and everything else happens automatically for you.
I'm working on getting IncludeNativeLibrariesForSelfExtract set by default, upvote here if you think that's a good idea: https://github.com/dotnet/sdk/issues/24181
In Single binary executable packages> and not an insignificant one.
And it's all due to how Code is both open-source in spirit and in truth, and aren't beholden to silly sales targets. You can see what this sort of thing does to a project when the Visual Studio 2022 team tried to move `dotnet watch` HMR functionality to Visual Studio 2022[0] instead of leaving it in VS Code.
0: https://github.com/dotnet/sdk/pull/22217
In Windows 11 Pro will soon require a Microsoft Account during initial setup