-
Notifications
You must be signed in to change notification settings - Fork 230
Proper workload support for 2xx #3705
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mthalman
merged 14 commits into
dotnet:release/10.0.2xx
from
mthalman:dev/mthalman/3126-workloads
Jan 9, 2026
Merged
Proper workload support for 2xx #3705
mthalman
merged 14 commits into
dotnet:release/10.0.2xx
from
mthalman:dev/mthalman/3126-workloads
Jan 9, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ViktorHofer
reviewed
Dec 9, 2025
ViktorHofer
reviewed
Dec 9, 2025
ViktorHofer
reviewed
Dec 9, 2025
ViktorHofer
reviewed
Dec 9, 2025
Member
Author
|
Reviewers: I need some eyes on this. Thanks. |
akoeplinger
reviewed
Dec 18, 2025
akoeplinger
reviewed
Dec 18, 2025
Make the 1xx experience (building shared components) the default by setting DotNetBuildSharedComponents=true in sdk's Directory.Build.props. Only pass /p:DotNetBuildSharedComponents=false to sdk when explicitly needed, reducing unnecessary build argument passing. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Document the purpose of this property to help prevent merge conflicts and clarify why this dependency exists for 2xx+ branches. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Clarify why MSI packages are marked as Internal when not building shared components - they are downloaded from 1xx builds and should not be republished. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Clarify why the Windows runtime packages have ExcludeAsMsi=true - they are included in the SDK directly and don't need MSI wrappers for workload installation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Member
Author
|
@ViktorHofer and @akoeplinger - PTAL at the updates. Need to get this in soon. |
ViktorHofer
reviewed
Jan 8, 2026
ViktorHofer
reviewed
Jan 8, 2026
ViktorHofer
reviewed
Jan 8, 2026
ViktorHofer
reviewed
Jan 8, 2026
ViktorHofer
approved these changes
Jan 8, 2026
Member
ViktorHofer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing my feedback
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements property workload support for the 2xx feature band. This does two things:
Example build containing the artifacts for inspection.
Fixes #3126