Fix import of x86 COM Component in ClickOnce #7324
Closed
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
John-Hart
approved these changes
Jan 24, 2022
|
Abandoning this PR since another PR (#7328) is out for dev17.1 branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fixes #
https://developercommunity.visualstudio.com/t/MSB3179:-Problem-isolating-COM-reference/1571958
Context
Import of x86 COM Component in Clickonce publish fails because msbuild is x64 process in dev17.
Changes Made
Fix code that's read COM registration data from registry to look in the Wow6432 node of HKCR as well.
Testing
Verifed with customer provided repro project that x86 COM component is imported fine after the fix.
Notes