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
Votive thinks BindInputPaths are content #4493
Comments
I just got this error message now after having edited the WiX project that outputs an msi file. I'm on version 3.9.1208.0. After reading this, I'm still not sure why I start getting this error now. After restoring my wixproj file from SVN, I still get the error message.
|
As a comment to my previous comment, my issue is now solved, and I can load my WiX project again. I don't know exactly what caused the error, but I found that it was somewhat related to a reference to %(AssemblyVersion.Version) in an out of scope PropertyGroup. This means it was not directly related to WiX. I changed my code to use the CreateProperty task, like shown below:
This made it possible to access the AssemblyToSign property outside the target in which it was defined.
|
I have a Bootstrapper .wixproj where I wanted to add BindInputPaths, so I added
This made VS2013/WiX 3.9.805 unable to load the project.
After looking through the code, the problem was that the path was absolute and outside of the project folder, so I made the path relative.
Now that VS could load the project, I saw that in Solution Explorer the folder was showing up as an item of the project with a warning symbol and link symbol. I noticed that the WiX toolset projects have their BindInputPaths in a .props file, so I tried moving the BindInputPaths into a .props file and import that in my .wixproj. That made Votive stop showing it, allowing me to change the path back to absolute.
Votive shouldn't be treating BindInputPaths as content.
The text was updated successfully, but these errors were encountered: