-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[release/11.0.1xx-preview1] Source code updates from dotnet/dotnet #52727
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
lewing
merged 9 commits into
release/11.0.1xx-preview1
from
darc-release/11.0.1xx-preview1-d8c0b1db-1909-4ac4-9af3-6a64d1e2f3d7
Feb 7, 2026
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
b76f223
Update dependencies
dotnet-maestro[bot] 54edac5
Update dependencies
dotnet-maestro[bot] 88861f7
Merge branch 'release/11.0.1xx-preview1' into darc-release/11.0.1xx-p…
DonnaChen888 9dc5b45
Update dependencies
dotnet-maestro[bot] 99cb42d
Add System.IO.Compression.ZStandard to WASM baselines
dsplaisted 605b2b8
Merge branch 'release/11.0.1xx-preview1' into darc-release/11.0.1xx-p…
DonnaChen888 4a5be3a
Update CSC arguments
jjonescz 966f25d
Update the canshow help baselines
marcpopMSFT 882951f
Backflow from build 20260204.18
ViktorHofer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
@jjonescz does this impact P1 meaning we should fix this for the produced P1 SDK?
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.
Aside from that, are there any plans to avoid these hardcodes?
Uh oh!
There was an error while loading. Please reload this page.
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.
If the DLL is supposed to be in P1, then without this change it won't be referenced by file-based apps that skip builds, yeah. (Sounds like a low priority edge case to me though.)
That would be straightforward to do technically I think but I would rather avoid that, that's why I chose this hard-coding in the first place; I have seen several times before that some unintended changes tried to slip through here - if this was automated, no-one would notice that. Also we only hardcode here the set of CSC arguments for the simplest command-line app. That should hardly ever change - if there is large change it's probably a bug - and so it seems like a good test in general to have (not just for file-based apps).
Uh oh!
There was an error while loading. Please reload this page.
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.
Looks like you hardcode all reference assemblies that are part of the microsoft.netcore.app.ref targeting pack. That will always change (grow). The source of truth is the ref pack's FrameworkList.xml file which provides the list of assemblies to reference and the TargetFrameworkVersion.
cc @ericstj for the ref pack
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.
I see, we can use that xml file instead of hardcoding the list of references, that makes sense to me.
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.
does the user have a way to target net10.0 with this? the System.IO.Compression.Zstandard.dll won't exist in that reference pack and looks like it'd also set
NET11_0_OR_GREATERdefineUh oh!
There was an error while loading. Please reload this page.
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.
They can set
#:property TargetFramework=net10.0or useDirectory.Build.propsor something like that - all of which will skip that optimized path (which uses hard-coded CSC args) and fallback to full MSBuild instead.Uh oh!
There was an error while loading. Please reload this page.
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.
@jjonescz since this PR is already merged, please file a tracking issue to capture our feedback around avoiding hardcodes
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.
#52934
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.
#53086