[release/10.0] Load Standalone GC correctly in component scenarios. #120235
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
AaronRobinsonMSFT
added
the
Servicing-consider
Contributor
|
Tagging subscribers to this area: @dotnet/gc |
jkotas
approved these changes
Sep 29, 2025
JulieLeeMSFT
added
Servicing-approved
JulieLeeMSFT
approved these changes
Sep 30, 2025
Member
|
@JulieLeeMSFT or @jeffschwMSFT can one of you merge this? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 #120012 to release/10.0
/cc @AaronRobinsonMSFT
Customer Impact
For scenarios involving .NET components the standalone GC name isn't respected properly.
Regression
Introduced in #101874
Testing
Validation of an "empty" string was introduced.
Risk
Low. This only impacts standalone GC scenarios, so the risk of any regression is minimal.