You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I reference this Setup project in my WIX Bootstrapper project, it says it cannot find "[OriginalFilename].msi" (LGHT0103). This is a major problem for me, since I really need the MSI filename to have the correct version number (which should be a common scenario). I encounter this error when using automated build with MSBuild. Not sure if it applies to Visual Studio.
I can see in the build log that candle.exe sets "-dSetup.TargetFileName" to the original filename.
Sure looks like a bug to me. Any chances for a fix?
Originally opened by znakeeye
The text was updated successfully, but these errors were encountered:
This is actually a limitation of using the BeforeBuild target in MSBuild. When a ProjectReference is resolved it gets the target name by calling the GetTargetName target. The BeforeBuild target is not included in the dependencies of GetTargetName.
If you want to modify the name of the MSI in the build, you'll need to find a way to insert a target in the dependencies of GetTargetName.
Alternatively, you could just name the MSI differently in the Bundle by providing a Name attribute.
Finally, modifying the MSI package name will require a major upgrade so changing the MSI package name is not generally recommended.
Originally posted by robmen Resolution set to by-design Status changed from Untriaged to Resolved
In My WIX Setup project I have a BeforeBuild target that updates the MSI output filename:
And this is the reference in the Bootstrapper project:
When I reference this Setup project in my WIX Bootstrapper project, it says it cannot find "[OriginalFilename].msi" (LGHT0103). This is a major problem for me, since I really need the MSI filename to have the correct version number (which should be a common scenario). I encounter this error when using automated build with MSBuild. Not sure if it applies to Visual Studio.
I can see in the build log that candle.exe sets "-dSetup.TargetFileName" to the original filename.
Sure looks like a bug to me. Any chances for a fix?
The text was updated successfully, but these errors were encountered: