[release/6.0] Environment variable should override property for gcServer. #61969
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 #61950 to release/6.0
/cc @AaronRobinsonMSFT
Customer Impact
This is a regression from .NET 5 to .NET 6 (when we consolidated complus_ into dotnet_ environment variable naming). The change in behavior has been observed by multiple customers.
The ASP.NET Core project default settings define the GC to operate in Server mode. However, Some customers prefer Workstation. The recommended approach to address this is setting
DOTNET_gcServer=0
, which will override the default configuration property. Without this change the only workaround is to edit the projectruntimeconfig.json
file via a template or set an MSBuild property.Testing
A test was added for the impacted scenario.
Risk
Low. The change is permitting a niche scenario for the overriding of configuration properties. The only known consumer of this change is the tested GC scenario.