dotnet / dotnet/msbuild

📝 Guidance for what an Sdk looks like

Open
#1,439 14 comments 5 reactions 0 assignees View on GitHub
needs-design triaged
Dominant language
C#
Stars
5.5k
Forks
1.5k
Avg merge
1d 8h
Merged PRs (30d)
141

Description

What makes a good Sdk? What functionality must it provide? Should it always include Common.targets? Should we define a new minimum target surface?

What do dependencies look like?

Must every Sdk have both props and targets? Should an Sdk define a version-number that can be used in other Sdks for error checking?

We should pull heavily from the experience of the existing Web and NET Sdks, but temper that with understanding that they were originally defined for something else.

Later edits:

- the following page contains samples of msbuild sdks, as well as links to documentation: https://github.com/Microsoft/MSBuildSdks

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.