This is an interesting circumstance. Chocolatey is a new way of deploying software packages, sort of like apt-get on Linux. Ordinarily, upgrading software that was previously installed via an MSI is easy. You just author a major upgrade into the next MSI or you create a patch. I'm not familiar with how Chocolatey works. If it just pulls the MSI down from the Web and installs it, then the same old tricks for upgrading should work. In other words, MSI's have an innate ability to find older versions of themselves to upgrade (as long as the UpgradeCode is the same and you've authored the necessary elements for the upgrade).
Automating an uninstall would require a ProductCode I think, if you need to do all of this from a PowerShell script. You can always install Orca.exe (from the Windows SDK I think: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\Orca.msi). This allows you to inspect an MSI package, which would let you see the Property table where the ProductCode is. In other words, once you've built the MSI, inspect it to get the ProductCode. Of course, there's nothing requiring you to use an asterisk as the Product element's Id. You could just create your own GUID and use it. Change it as necessary for upgrade packages. Be interested for you to post more on this forum about Chocolatey. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Product-Id-tp7583827p7583876.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
