A while back I posted a guide on how to get WiX to automatically set the installation package’s version, and how to rename the output package to include the same version number.
The instructions still work great, but it all felt a bit too messy.
I’ve spent a bit of time with WiX 3.5 over the last few days (because only WiX 3.5 beta supports Visual Studio 2010), and I’ve been able to solve a few niggling issues with my previous installers. Cleaning up how I name the output package is one of those.
I’m still doing this for the version number of the installer, (where $(var.xx.TargetFileName) points to a Project Reference*):
Name="Blackbox for Windows Home Server"
Manufacturer="Tentacle Software Ltd."
But I’m now using a different method to rename the actual output file to include the version number, and have that automatically update whenever the version of the project changes.
The basic issue was that I couldn’t work out how to make the WiX processors pick up changes to the OutputName property of the wixproj file, so I was left with running an action after the build to rename the output file to what I wanted.
The old and busted way:
<Output TaskParameter="Assemblies" ItemName="AssemblyVersion"/>
<Copy SourceFiles=".\bin\$(Configuration)\$(OutputName).msi" DestinationFiles=".\bin\$(Configuration)\WHSDiskManagement.%(AssemblyVersion.Version).msi" />
<Delete Files=".\bin\$(Configuration)\$(OutputName).msi" />
The new hotness:
<Output TaskParameter="Assemblies" ItemName="AssemblyVersions" />
<Output TaskParameter="Value" PropertyName="TargetName"/>
<Output TaskParameter="Value" PropertyName="TargetFileName"/>
<Output TaskParameter="Value" PropertyName="TargetPath"/>
You can see I’m still using GetAssemblyIdentity and pointing to the assembly whose version number I want to grab, but I’ve switched to a BeforeBuild action. That’s because I figured out I could explicitly change the command parameters that WiX was sending – specifically, the TargetName, TargetFileName, and TargetPath variables, which determine the final file name of the package.
In the example above, I’m taking the OutputName that I configured in the project properties (“TentacleSoftware.Blackbox” in this case), and appending the version number to it to create my new TargetName.
There’s a few more lines of XML there, but basically after we set the TargetName property we’re just rebuilding the TargetFileName and TargetPath properties to match.
Interestingly, my initial tests showed that I didn’t have to update anything except the TargetName – the TargetFileName and TargetPath were still the ‘incorrect’ values but the output file included the version number anyway – but to be on the safe side, I’ve chosen to rebuild all the Target* properties so that they’re valid.
That all feels lots cleaner to me. We’re actually setting the desired output name and letting WiX take care of the rest, rather than renaming files at the end.
*More about Project References, and why I should have been using them ages ago, soon.