dotnet/sdk

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

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 21st, 2026
Created on July 22nd, 2016
Open Issues & Pull Requests: 2,450 (+1)
GitHub issues: Enabled
Number of forks: 1,289
Total Stargazers: 3,219 (+0)
Total Subscribers: 212 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.8 hours
Mean response time: 27.7 days
90th percentile: 30.8 days
Tracked items: 5,519

How this project is maintained

About 16% of issues opened in the past year have never received a reply. 58% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "untriaged" is answered fastest, typically in about 6 hours, while "Area-dotnetup" waits about 4 days. 64% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 55% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,734
New in 7 days: 9
Closed in 7 days: 16
Avg open age: 742 days
Stale 30+ days: 1,557
Stale 90+ days: 1,176

Recent activity

Opened in 7 days: 4
Closed in 7 days: 14
Comments in 7 days: 13
Events in 7 days: 34

Top labels

  • untriaged (1,452)
  • stale (951)
  • Area-NetSDK (719)
  • Area-CLI (332)
  • Area-Infrastructure (332)
  • Area-Workloads (302)
  • Area-dotnet test (227)
  • Area-Tools (205)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

The .NET SDK is a command-line and build tool that provides core functionality shared between Visual Studio and the .NET CLI for creating .NET projects.

The tool solves the problem of providing a unified set of build tasks and project templates across different .NET development environments. It accomplishes this by centralizing MSBuild tasks under a shared codebase that both Visual Studio and the .NET CLI consume, rather than maintaining separate implementations. The SDK includes common project and item templates alongside the build infrastructure needed to compile and package .NET applications.

Developers should adopt this tool if they are building .NET projects and want consistency between command-line and IDE-based workflows. It suits any .NET development scenario where you need reliable, shared build behavior across tools. The project is particularly relevant for teams using both Visual Studio and dotnet CLI, as it ensures the same underlying build logic powers both environments. Visual Studio-specific project system work is maintained separately in a dedicated repository, so this SDK focuses on the cross-platform, cross-tool concerns.

The project maintains public and internal build pipelines with visible status reporting. Contributions are actively managed through area-based labeling and codeowner assignment to route issues and pull requests to appropriate maintainers. The repository provides a developer guide for building the SDK locally and includes a dogfooding script that allows testing locally-built versions across Visual Studio, dotnet CLI, and MSBuild. Pull request timelines are documented to help contributors understand version-specific deadlines for their changes.