[release/10.0.2xx] ProcessFrameworkReferences: use portable ILCompiler when RuntimeIdentifier is null.#52486
Merged
baronfel merged 7 commits intorelease/10.0.2xxfrom Jan 27, 2026
Conversation
baronfel
approved these changes
Jan 20, 2026
…times if it's empty (#52685) Co-authored-by: Marc Paine <marcpop@microsoft.com>
Member
|
/ba-g known template engine macos ssl error |
Member
|
@baronfel FYI, it looks like in addition to the templating issue on this one there were some leg timeouts which we've started seeing, not sure what's going on with them yet. |
Member
|
Oh good grief, and because they were canceled they didn't block the merge? |
1 similar comment
Member
|
Oh good grief, and because they were canceled they didn't block the merge? |
3 tasks
This was referenced Feb 12, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Backport of #52407 to release/10.0.2xx
Fixes #52395
Fixes #42335
Customer Issue
Users trying to publish NativeAOT applications on source-built SDKs would error because the tooling always directed them to non-portable versions of the NativeAOT tooling - which may not be present in the installs. The desired semantic is that the source-built AOT tooling should only be used when targeting the non-portable RID associated with the source-built SDK platform.
Description
This PR ensures that on all SDKs, the 'portable' version of the AOT tooling is used when no explicit RID is chosen for targeting. This means that by default applications that users build with NativeAOT will user Microsoft binaries from NuGet. Users that specifically want to target non-portable RIDs (e.g.
fedora.x.y) must specify that RID explicitly.Was this a regression?
Testing
A new test has been added that explicitly maps out the expected behaviors:
Risk
Low - there is broader testing coverage of asset selection now and this pathway continues to work as expected for all other AOT/Trimming related publishing tests.