[release/6.0] Update COM host to match RegAsm registration behavior #63318
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
ghost
added
the
|
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsBackport of #63292 to release/6.0 Customer ImpactTestingRisk
|
AaronRobinsonMSFT
added
the
Servicing-consider
jeffschwMSFT
approved these changes
Jan 3, 2022
leecow
added
Servicing-rejected
and removed
Servicing-consider
|
Good for .NET 7 but does not meet bar for 6.0 |
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 #63292 to release/6.0
Customer Impact
Customer reported in #62529. The issue is the name of the server in the registry was the same for all managed COM servers. This changes it to match RegAsm and
RegistrationServices. Presently, the same name is used for all COM servers written in managed code, "CoreCLR COMHost Server". This means that when someone is looking the Registry, they see that in the default value of the GUID key instead of the type name, as was the case using RegAsm. This has no functional change but has quality of life impact and is nice to match the existing tooling behavior in .NET Framework.Testing
Validated the type is properly set.
Risk
Low. This is a non-functional change and is purely for COM tooling UX and other Registry probing user scenarios.
/cc @elinor-fung