[release/8.0] [browser] Fix processing of satellite assemblies from referenced assembly during publish#109920
Merged
carlossanlop merged 2 commits intodotnet:release/8.0from Dec 2, 2024
Merged
Conversation
maraf
added
arch-wasm
Member
|
Is this ready? |
maraf
requested review from
akoeplinger,
ilonatommy and
lewing
and removed request for
radical
ilonatommy
approved these changes
Nov 26, 2024
lewing
added
Servicing-approved
Member
|
@carlossanlop we need this one |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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 #106696 to release/8.0
Fixes #109604
Customer Impact
This PR fixes publishing satellite assemblies in (Blazor) WebAssembly apps using .NET 9+ SDK.
Regression
Regression from #90436.
Testing
This particular cross version scenario was tested manually, along with not affecting using the workload with .NET 8 SDK. Running automated tests for the cross version scenario is problematic because of how we version the runtime, tracking in #110049.
Risk
Medium to low. Affected scenarios are covered with automatic tests. What we don't have covered with automatic tests is cross SDK and workload scenario.