Looking forward to playing with 'dotnet run app.cs' instead of PowerShell.
It'll probably not be really useful until multiple files support arrives in .NET 11:
https://github.com/dotnet/sdk/issues/48174
In .NET 10 Preview 6 brings JIT improvements, one-shot tool executiondotnet
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
5 sources> From a user perspective, "dotnet run" does add a new scripting dialect.
By dialect I mean that in CSX, the C# language has subtle differences in behavior compared to CS files (e.g., top-level methods are compiled differently). In 'dotnet run app.cs', the C# is exactly the same, hence it can be converted to a project (and we have a command for that - 'dotnet project convert').
> It's just a preprocessor - not a change to the C# syntax.
Should #:load work in normal C# files as well then? If yes, we would have two ways to include files - the normal way (include them in the project) or via #:load. If not, how would 'dotnet project convert' work? (It could paste the text but that's not very DRY if it's imported at multiple places.)
That's in short why #:load doesn't play very nicely with existing C# (it's a different paradigm of including ot
Read the rest
her files). So the current proposal is to just make files in the same folder visible (just like they would be for a .csproj), because that's consistent with current C#, 'dotnet project convert' works, etc. But this proposal is not final yet, there are other options including what you suggest - see https://github.com/dotnet/sdk/issues/49193.
> You can't do much of anything in .NET without referencing Nuget assemblies.
And referencing NuGet assemblies is of course supported via the #:package directive. It's just that referencing DLLs directly is not a common scenario, hence it's not supported for now (but can be added later).
> Agreeing with others, '#r "nuget:' should at least be an option.
Thanks, we hear you and plan to add support for it, see https://github.com/dotnet/sdk/issues/49199
> And otherwise (but I guess regarless if you stick with this syntax) you will have to add another tab to Nuget called "dotnet run". "Script & Interactive" is already present in Nuget and shows the #r syntax for a reference.
Agree but also note that the ".NET CLI" tab which tells you to run "dotnet add package" should also work in near future, see https://github.com/dotnet/sdk/issues/49200.
In Run a C# file directly using dotnet run app.csI opened an issue since I couldn't find docs that indicate what they were working on to improve the start time, and they replied:
https://github.com/dotnet/sdk/issues/49197
In Run a C# file directly using dotnet run app.csThere is even more info in the proposal itself https://github.com/dotnet/sdk/blob/main/documentation/genera... specifically things about multiple files and more specifics of the implementation and capabilities (implicit project file etc)
In Run a C# file directly using dotnet run app.cs