mirror of
https://github.com/finos/SymphonyElectron.git
synced 2024-12-27 17:31:36 -06:00
| .. | ||
| Files | ||
| Build.cmd | ||
| CustomAction.config | ||
| EmbeddedUI.config | ||
| MajorUpgrade1.pdb | ||
| MyProduct - Copy.wxs | ||
| MyProduct.wixobj | ||
| MyProduct.wxs | ||
| readme.txt | ||
| setup.1.cs | ||
| setup.1.cs.dll | ||
| setup.1.msi | ||
| setup.1.wixpdb | ||
| setup.2.cs | ||
| setup.2.cs.dll | ||
| setup.2.msi | ||
| setup.2.wixpdb | ||
| setup.cs | ||
| setup.cs.dll | ||
| setup.msi | ||
| setup.wixpdb | ||
| TestProduct.dialog_banner.png | ||
| TestProduct.dialog_bmp.png | ||
| TestProduct.licence.rtf | ||
| TestProduct.wixobj | ||
| TestProduct.wxl | ||
| TestProduct.wxs | ||
| uninstall.cmd | ||
| WixSharp.CA.dll | ||
This sample demonstrates how to implement MajorUpgrade deployment scenario. * Implementing with MajorUpgrade element (recommended) It is the current WiX technique, which has been introduced in WiX v3.5 to replace more complicated Upgrade element. - Execute build.cmd file to build setup.msi file. - Install setup.msi - Observe "1.0.209.10040" version being installed in "Programs and Features" - Increase version (e.g. "1.0.209.10040" -> "1.1.209.10040") in the setup.cs - Execute build.cmd file to build setup.msi file. - Install setup.msi - Observe "1.1.209.10040" version being installed in "Programs and Features" * Implementing with Upgrade element It is an older technique, which has been superseded by simplified MajorUpgrade element in WiX v3.5. Execute build.cmd file to build msi files (setup.1.msi and setup.2.msi) for two versions of the same product. Then execute the setup.1.msi to start the installation of the version 1.0.0. After that execute the setup.2.msi. Note installation of version 2.0.0 will automatically uninstall version 1.0.0