-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Add script to rebuild component refs #11485
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
|
This run produced the fixed wix file: https://dev.azure.com/powershell/PowerShell/_build/results?buildId=42371&view=artifacts&type=publishedArtifacts |
|
@TravisEz13 Can you please update the PR description to include some context information about this change? |
|
I am missing the context as well. Usually, I've used the auto-generated WiX file that |
|
@bergmeister is you used the autogenerated files, then you are not the cause. Someone did not and the ComponentGroup section of the file did not contain all the updated components. |
|
This happened in the fork we used to update to .NET Core 3.0. We squash merged that fork, so.... I cannot tell where exactly the issue occurred. |
* Add script to rebuild component refs * fix type * fix document we get componentGroup from * update files.wxs * fix dependencies
|
🎉 Handy links: |
PR Summary
Add script to rebuild WIX component refs
PR Context
Someone (cc @SteveL-MSFT, @bergmeister), let the WIX file fragment be edited by hand and become corrupt.
This script examines the WXS fragment and looks for the corruption, fails the build, and outputs and correctly built WXS fragment.
Note, Please do not hand edit the files.wxs file. Always let the CI system, find the problems and fix them.
If you try to hand edit, you risk us not being able to issues a security patch if needed.
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.