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.
I ran into an interesting scenario related to Windows Installer major upgrades recently and I wanted to summarize some things I learned from this experience and from the MSDN documentation in case they are useful for others. In the scenario I ran into, I implemented a Windows Installer major upgrade to automatically remove older versions of my MSI behind the scenes as part of the installation process for newer versions of my MSI.
I scheduled the uninstall of the previous version after InstallFinalize due to the assembly publishing issue described in this blog post. This scheduling resulted in the newer version being installed before the older version was uninstalled. However, I needed a way to prevent some of the custom actions in the older version from running during this major upgrade uninstall step because they would interfere with the already installed newer version.
Fortunately, I was alerted to the existence of the UPGRADINGPRODUCTCODE property in Windows Installer. When Windows Installer removes an older version of a product in the RemoveExistingProducts action as part of a major upgrade, it sets the UPGRADINGPRODUCTCODE property on the command line for the uninstall action. This property can be used by the MSI being uninstalled to differentiate between a standard uninstall initiated by the user (via Add/Remove Programs for example) and an uninstall initiated by a newer version of the MSI via a major upgrade.
What I ended up doing was adding a condition of (NOT UPGRADINGPRODUCTCODE) in the InstallExecuteSequence table for each of the custom actions that I wanted to prevent from running during the major upgrade. This allowed my major upgrade to work as expected and prevented the uninstall of the older version from breaking the newer version. It also allowed a standard uninstall of the MSI to correctly execute these custom actions.
Thanks to Heath Stewart for letting me know about the UPGRADINGPRODUCTCODE property to help out in this scenario.
HI, I am Sonali and am not sure if this is the right place to ask this question, If its not, am sorry to bother you... I am working on a tool written in VB.NET. I added a setup project to it. The project ran fine untill I reorganized my reference dll's and other files to a different directory structure. Ever since then, the msi gets installed but app fails to launch. Please can you help me understand what is the problem and/or resolution??
Hi Sonaliagrawal - You will need to debug your application after installing the MSI to figure out why it is failing to launch. It is likely not able to find some of its dependent DLLs after you moved them to a new location, and you may need to revert that change or make some additional changes to your MSI to correct this problem.
One of the features included in the WiX v3.0 source files included in the C# project template in the
PingBack from http://msdnrss.thecoderblogs.com/2007/09/07/subtle-problem-with-major-upgrades-in-wix-files-in-the-media-center-sdk-2/
When I create an MSI-based installer, one of the things I typically include in the setup authoring is