docs(sdk): design standardized solution setup - #920
Conversation
Co-authored-by: AndreaCuneo <5227688+AndreaCuneo@users.noreply.github.com>
Co-authored-by: AndreaCuneo <5227688+AndreaCuneo@users.noreply.github.com>
AndreaCuneo
left a comment
There was a problem hiding this comment.
@copilot update the design based on the answered questions. Improve the details of the one still open and do another feedback round.
Co-authored-by: AndreaCuneo <5227688+AndreaCuneo@users.noreply.github.com>
Updated in eb97110. Accepted answers now drive the stable design; the second feedback round is reduced to four expanded open decisions covering distribution, SDK composition, MTP/framework boundaries, and package-version ownership. |
AndreaCuneo
left a comment
There was a problem hiding this comment.
@copilot if needed do another feedback round
Co-authored-by: AndreaCuneo <5227688+AndreaCuneo@users.noreply.github.com>
Co-authored-by: AndreaCuneo <5227688+AndreaCuneo@users.noreply.github.com>
A third feedback round is needed for one verified hybrid boundary only: SDK-24 asks whether |
Co-authored-by: AndreaCuneo <5227688+AndreaCuneo@users.noreply.github.com>
Co-authored-by: AndreaCuneo <5227688+AndreaCuneo@users.noreply.github.com>
Ark.Tools consumers currently copy build conventions and analyzer configuration from sample projects, causing configuration drift. This proposes a versioned distribution model for those shared defaults.
Architecture
buildTransitiveapproaches.Ark.Tools.Sdkbecause it supports conditional package references without leaking policy transitively.Current-state inventory
External research
Meziantou.NET.Sdkand its deprecated CodingStandard predecessor.Decision record