Repository files navigation

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/.

Seedotnet/project-system for the project system work that is specific to Visual Studio.

Common project and item templates are found intemplate_feed.

Visibility	All jobs
Public
Microsoft Internal

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

<configuration>  <packageSources>    <addkey="dotnet10"value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet10/nuget/v3/index.json" />  </packageSources></configuration>

<configuration>  <packageSources>    <addkey="dotnet9"value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json" />  </packageSources></configuration>

<configuration>  <packageSources>    <addkey="dotnet8"value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json" />  </packageSources></configuration>

Our Debian packages are put together slightly differently than the other OS specific installers. Instead of combining everything, we have separate component packages that depend on each other. If you're installing the SDK from the .deb file (via dpkg or similar), then you'll need to install the corresponding dependencies first:

• Host, Host FX Resolver, and Shared Framework
• ASP.NET Core Shared Framework

Sources for dotnet-install.sh and dotnet-install.ps1 are in theinstall-scripts repo.

We welcome you to try things out,file issues, make feature requests and join us in design conversations. Be sure to check out ourproject documentation

This project has adopted the.NET Foundation Code of Conduct to clarify expected behavior in our community.

Start with theDeveloper Guide.

To test your locally built SDK, runeng\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

Please see thePull Request Timeline Guide.

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 usingArea- labels. Then we rely on thecodeowners 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 viewedhere

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.

The .NET SDK project uses theMIT license.

TheLICENSE.txt andThirdPartyNotices.txt in any downloaded archives are authoritative.