-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Make sure SharedFx & TargetingPack msi names match #28298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Check the wixlib authoring. I seem to remember it referencing the MSI name using the project reference, but I'm almost certain it's using the project.outputname, so we should be good then. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but we just need to confirm the wixlib reference
7def3b8
to
e1e676b
Compare
@JunTaoLuo @joeloff please re-review - the previous issue was that |
And PackageName should remain consistent when it's doing the copy/rename later on? Or is that a potential issue to deal with in the future if something gets renamed? |
Do you mean |
Ok, as long as the target runs for each project separately, then
|
The .msi is now named |
* Make sure SharedFx & TargetingPack msi names match * Insert packageVersion into OutputName when available * Move props around again
Resolves #28029. The name of the standalone .msi's here weren't matching what gets into VS, meaning that you can't repair a VS installation with the standalone bundle. The solution is to make sure the names match in both places (the .msi should be versioned)