Enable MSI upgrades rather than side-by-side install - #4259
Conversation
|
Steve Lee (@SteveL-MSFT) Changes look good. The only thing is to watch out for is that the 'ProductGuid' needs to be the same if you need upgrade to be supported. For major version changes, ProductGuid can be changed |
|
Raghu Shantha (@raghushantha) currently, |
|
Steve Lee (@SteveL-MSFT) or Raghu Shantha (@raghushantha) It's great to have upgradability support but does this mean that we lose the ability of having multiple version installed side-by-side? We use older versions of PowerShell Core in our CI system (that is locked down and therefore not updated unless needed) and I always found it handy being able to repro on my local machine using the same version that is being used in CI in order to replicate the exact same behaviour. |
|
ChristophB125 You can still have side-by-side by downloading the zip and extracting the contents in a secure location (this will always be supported). |
|
Thanks for the info. The self contained version in a zip file should be sufficient for our use case. |
MSI only works against A.B.C type version strings. So to enable beta.X to beta.X+1 upgrades, we have to use the
AllowSameVersionUpgradesas they are all effectively 6.0.0 from MSI point of view.Note that to get Wix toolset working on Win10, you may have to pass
-svalto light.exe.Fix #3946