Skip to content
/ sdk Public
forked from dotnet/sdk

Core functionality needed to create .NET Core projects, that is shared between Visual Studio and CLI

License

Notifications You must be signed in to change notification settings

nagilson/sdk

This branch is 46043 commits behind dotnet/sdk:main.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

4beabef · Mar 21, 2023
Feb 21, 2023
Feb 15, 2023
Feb 24, 2023
Mar 21, 2023
Aug 28, 2020
Mar 9, 2023
Mar 6, 2023
Jan 31, 2023
Dec 2, 2019
Sep 9, 2021
Aug 8, 2022
Feb 7, 2023
Feb 15, 2023
Apr 2, 2020
Feb 14, 2023
Nov 18, 2022
Feb 1, 2023
Mar 26, 2019
Nov 11, 2022
Feb 24, 2019
Mar 8, 2023
Feb 28, 2020
Nov 23, 2022
Sep 20, 2018
Oct 30, 2021
Feb 22, 2023
Sep 19, 2018
Oct 30, 2021
Jan 10, 2023
Dec 14, 2022
Sep 19, 2018
Oct 30, 2021
Sep 21, 2022

Repository files navigation

Welcome to dotnet sdk

This repository contains core functionality needed to create .NET projects that is shared between Visual Studio and the .NET CLI.

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

Common project and item templates are found in template_feed.

Build status

Windows x64

Installing the SDK

Official builds

Latest builds

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.

About

Core functionality needed to create .NET Core projects, that is shared between Visual Studio and CLI

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C# 96.9%
  • PowerShell 1.3%
  • Shell 0.9%
  • HTML 0.7%
  • JavaScript 0.1%
  • CMake 0.1%