Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS with no warranties, and confer no rights. Additionally, views expressed herein are my own and not those of my employer, Microsoft.
Peter Marcu posted a couple of items on his blog recently that I wanted to link to here so hopefully more folks will see them. The first is a high-level description of new patching features that have been added to WiX v3.0 over the past few months. You can find the post at http://blogs.msdn.com/pmarcu/archive/2007/06/16/wix-building-a-patch-using-the-new-patch-building-system-part-2.aspx. It briefly introduces the old and new ways to create patches using WiX.
The second is a really nice example of how to create a patch using the new features in WiX v3.0. You can find this blog post at http://blogs.msdn.com/pmarcu/archive/2007/06/28/sample-patch.aspx. To summarize Peter's post, the following are the steps that can be used to create your first patch:
If you are a setup developer interested in creating patches for your MSI-based installers, I encourage you to check out Peter's blog posts for more detailed information about how to use new features in WiX v3.0 to create patches.
<update date="7/17/2007"> Updated step 7 to indicate that the output file is a .wixmst file and not a standard Windows Installer .mst file </update>
Actually, in step 7 you create a wixmst, which is just a wixout for transforms. The extension doesn't matter really, of course. A wixout is perfectly acceptable.
Hi Heath - Good catch, that was a typo when I was summarizing Peter's list of steps. I've updated the text of my blog post with this to avoid confusion.
Since my last update some changes have appeared in the steps needed to create a patch using Wix. The...