major-upgrade

Run Wix Custom action only during uninstall and not during Major upgrade

由 …衆ロ難τιáo~ 提交于 2020-01-09 03:56:26
问题 I am trying to delete a file using a custom action scheduled between InstallInitialise and InstallFinalize standard action. MajorUpgrade element is used to design upgrades. However, I want the custom action to run only during uninstall and not during the Major upgrade(this includes uninstall and install). I have used the following conditions to execute the CUstom action: (NOT UPGRADINGPRODUCTCODE) AND (REMOVE="ALL") REMOVE AND NOT WIX_UPGRADE_DETECTED Is there a way to uniquely detect the

WiX Bundle: Patches for 1.0.0 are not removed from Programs & Features when bundle 2.0.0 is installed

由 别来无恙 提交于 2019-12-25 08:05:08
问题 There are 3 bundles, code is listed below. 1.0.0, 1.0.0.1, and 2.0.0. If 1.0.0, 1.0.0.1, and 2.0.0 are installed, View Installed Updates will still have 1.0.0.1 listed as installed. It will remain there until the last Version is uninstalled. <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Bundle Name="Burn Installer" Version="1.0.0" Manufacturer="LANSA" UpgradeCode="AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA" Copyright="..." AboutUrl="..."> <BootstrapperApplicationRef Id=

Major Upgrade without uninstallation of Windows Service

由 给你一囗甜甜゛ 提交于 2019-12-24 21:28:27
问题 I am really very sorry for being redundant. I have checked a lot of other posts in this site itself and perhaps some other sites. I am not able to get Major Upgrade working without uninstalling & reinstalling of service. I am changing the Product Code and Version and the UpgradeFileComponent is the component that is part of the Upgrade. All the remaining are the same as in 1.0.0. I am doing a POC and hence would like to make only this small change (not as a patch, but as a major upgrade).

How to prevent Wix from installing an older version?

由 為{幸葍}努か 提交于 2019-12-18 09:24:09
问题 I have an application that we are switching over to a WiX installer. So far almost everything seems to be going well. The one problem I'm having is that if an older version is downloaded and attempted to install, it does so. And that's a bit of a problem. If there is a newer version installed I don't want it to install the older version. I thought the problem was with the "Upgrade" component but I must admit I've hit a wall. How can I change it so that the older versions see there is a newer

Adding entries to MSI UpgradeTable to remove related products

由 雨燕双飞 提交于 2019-12-17 05:15:10
问题 A WiX installer product node has an attribute UpgradeCode. It is used to refer to previous versions of the same product. The value is stored in the UpgradeTable. The UpgradeTable is parsed by the FindRelatedProducts action. The UpgradeCode allows to remove previous products with the same UpgradeCode . But the plan is to integrate several outdated legacy product to a combined single product. The UpgradeCode of this legacy product is known. I hope adding this code to the UpgardeTable will

Detecting MajorUpgrade in Wix 3.8

由 谁都会走 提交于 2019-12-13 14:19:18
问题 I am installing all new versions of my software as major upgrades, as the installations are very small and most of the time, all files change anyway. I would like to skip one dialog in the installer, if an upgrade as compared to a fresh installation is done, but so far I have failed to figure out what conditional (like "Installed AND PATCH") in the following example to use. <Publish Dialog="VerifyReadyDlg" Control="Back" Event="NewDialog" Value="WelcomeDlg" Order="2">Installed AND PATCH<

WiX Installer: getting version of the product being upgraded

由 对着背影说爱祢 提交于 2019-12-11 02:49:39
问题 During a major upgrade from version X to version Y, I need to have a property/variable stating that version X is being upgraded. When performing a Major Upgrade of a product with a setup built by WiX Installer, is there a way to get the version number being upgraded? 回答1: Assuming you're using a WiX majorupgrade element, when an upgrade is detected the value of the WIX_UPGRADE_DETECTED property is set to the productcode of the product being upgraded. You could pass that into the C++ Win32 API

Wix major upgrade, replace files regardless of newer file version

由 别来无恙 提交于 2019-12-07 02:50:17
问题 My WiX installer (Wix 3.10, MSI 4.5) uses MajorUpgrade for updating. The files to be installed are harvested with heat.exe in pre-build. The current (older) msi file contains a file nlog.dll (which came with a NuGet package v4.1.0 ) that has a file version of 4.1.0.0 , a product version of 4.1.0 and last write time of 2015-09-01 . Since the nlog team ran into some strong naming issues, they published an updated NuGet package v4.1.1 , containing an updated nlog.dll with its file version

Wix major upgrade, replace files regardless of newer file version

由 无人久伴 提交于 2019-12-05 07:25:07
My WiX installer (Wix 3.10, MSI 4.5) uses MajorUpgrade for updating. The files to be installed are harvested with heat.exe in pre-build. The current (older) msi file contains a file nlog.dll (which came with a NuGet package v4.1.0 ) that has a file version of 4.1.0.0 , a product version of 4.1.0 and last write time of 2015-09-01 . Since the nlog team ran into some strong naming issues, they published an updated NuGet package v4.1.1 , containing an updated nlog.dll with its file version decreased back to 4.0.0.0 while its product version has been increased to 4.1.1 , last write time is 2015-09

WiX MajorUpgrade of Windows Service, preserving .config, and avoiding a reboot

由 ∥☆過路亽．° 提交于 2019-12-04 18:50:52
问题 I am struggling to get MajorUpgrade, ServiceControl, .config files to work nicely together. After my other question, I'm now kinda having the opposite problem again. Before, the files weren't being overwritten because the AssemblyFileVersions were static so I fixed that. 1) Now, even with Schedule="afterInstallExecute" my KeyPath='yes' .config file is still being overwritten even though the existing file modified date is different than the file creation date and it is set as a KeyPath. I'm
订阅 major-upgrade