-
In WiX V3 it was pretty common to have something like this fragment to set the name of the output and it's pdb:
I now see in the V4 wixproj that these settings were preserved but a new property called OutputName is defined that drives the output. I tried commenting the propertygroup that defined outputname and then replacing TargetName with OutputName as shown, but I got outputs named after the project name:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
WiX v3 took a very old version of an MSBuild targets file and adapted it to the needs of the toolset. That resulted in newer features in later versions of Visual Studio, MSBuild, etc. not being available or simply not working when introduced into other projects in the same solution. WiX v4 integrates into the Microsoft-provided plumbing for SDK integration, taking advantage of all the new features (such as new-style project files,
What I've seen suggested in stackoverflow for other project types in MSBuild is to have a target rename the output file, if the above isn't possible. |
Beta Was this translation helpful? Give feedback.
WiX v3 took a very old version of an MSBuild targets file and adapted it to the needs of the toolset. That resulted in newer features in later versions of Visual Studio, MSBuild, etc. not being available or simply not working when introduced into other projects in the same solution.
WiX v4 integrates into the Microsoft-provided plumbing for SDK integration, taking advantage of all the new features (such as new-style project files,
PackageReference
s, etc.), which means that common properties and targets will now work as they do for other project types using the new-style project file format.OutputName
is used to set a lot of other related properties and items early on, before any targets …