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
Certain registry keys cause link to fail unless linker is run as administrator #4753
Comments
The problem is the backslash at the end of
|
What I am feeling might be akin to buyer's remorse, but here goes, anyway. In the first entry for this issue, I note that the command: C:\Program Files (x86)\WiX Toolset v3.8\bin\candle.exe -dDebug -d"DevEnvDir=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\" -dSolutionDir=C:\Users\Autobuild\BUILD\WixBug\ -dSolutionExt=.sln -dSolutionFileName=WixBug.sln -dSolutionName=WixBug -dSolutionPath=C:\Users\Autobuild\BUILD\WixBug\WixBug.sln -dConfiguration=Debug -dOutDir=bin\Debug\ -dPlatform=x86 -dProjectDir=C:\Users\Autobuild\BUILD\WixBug\WixBug\ -dProjectExt=.wixproj -dProjectFileName=WixBug.wixproj -dProjectName=WixBug -dProjectPath=C:\Users\Autobuild\BUILD\WixBug\WixBug\WixBug.wixproj -dTargetDir=C:\Users\Autobuild\BUILD\WixBug\WixBug\bin\Debug\ -dTargetExt=.msi -dTargetFileName=WixBug.msi -dTargetName=WixBug -dTargetPath=C:\Users\Autobuild\BUILD\WixBug\WixBug\bin\Debug\WixBug.msi -out obj\Debug\ -arch x86 Product.wxs contains a double backslash at the end of the -d"DevEnvDir ... " option. Is this an issue? There are also trailing backslashes on other paths specifying folders. These are generally valid, but they are still edge cases subject to suspicion. How was the registry key in the project file created? was it typed into the project file by the user or created by an automated process? The only distinction I saw between running Visual Studio elevated or not was that registry path validation was bypassed when the process was elevated. In this report, the claim is that the failure only occurs when the execution is elevated. Are we fixing the wrong bug? |
No need to worry about squashing the commit history. I've redone my changes twice. Its probably been at least 20 years since I used VI, and I've never used VIm. When Vim popped up during a "git rebase -i", I lost it. I should have check the editor setting. (I still haven't.) I knew that the default setting was Vim, but I also saw references to notepad, which I thought might be the Windows default. I don't know if it is. Perhaps you overrode it. Then I fixed everything up and watched a git reset eat my changes. I finally got control of the situation on my third try. I'm starting to feel a little more comfortable with running git with remotes. I'm certainly getting enough practice. |
Those are quoted paths on the command line to candle, the trailing double backslash escapes the backslash so the quote isn't escaped. You can experiment with the same thing from a cmd prompt. None of that has anything to do with the registry keys. The registry keys issue comes from developer mistakes and/or poor concatenation of need registry keys. |
Learning git in a brand new personal repository is probably a lot easier than trying to work in something with as much history as the WiX Toolset. |
Product definition below fails to build with the following errors.
There is one workaround:
Project:
The text was updated successfully, but these errors were encountered: