Hey. According to the Windows Installer specifications, we change the Product Code of our product with every release (We just use <Product Id="*" ... />) and we keep the Upgrade Code the same. That way, when the individual MSIs are run, if any previous versions exist, they are first uninstalled.
At the moment, we're making a bootstrapper for our products, and in this process, we're also making a custom managed GUI. It detects if a product is already installed (its PackageState is reported as PackageState.Present) or not installed (PackageState.Absent). However, if a product is installed, but the bootstrapper contains a newer version of the product, it is reported as PackageState.Absent, not PackageState.Superseded, like one would expect. Is there anything in particular we need to do in order to get this upgrade detection mechanism to work? Best regards ALEXANDER K. SCHRØDER ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
