wix3.7

WIX enable Windows feature

时光总嘲笑我的痴心妄想 提交于 2019-12-01 05:16:55
问题 I have to check if some windows features are enabled beore installing my software. I can check it or install it using dism command line tool. I create a custom action to do this, but is there a way to do it in a "WIX native way" ? <Property Id="dism" Value="dism.exe" /> <CustomAction Id="InstallMSMQContainer" Property="dism" ExeCommand=" /online /enable-feature /featurename:MSMQ-Container /featurename:MSMQ-Server /featurename:MSMQ-ADIntegration" Return="check" Impersonate="yes" Execute=

Wix Burn: How to stop Bootstrapper from installing itself

自作多情 提交于 2019-12-01 04:39:08
问题 I believe this question might have been asked before me, but somehow, I'm not finding some appropriate answer. I may have to write my own managed bootstrapper. But up-till now, in the examples I got, the bootstrapper is installing itself as well and appearing in Add-Remove programs instead of my product. Question: Can we make bootstrapper to only install our products and pre-requisite applications and not to install itself? Regards 回答1: No. Burn is not a "fire and forget" bootstrapper. See

WiX Burn after restart/force reboot continuing installation

不羁的心 提交于 2019-11-30 22:18:05
I have a WiX Burn custom installer using ManagedBootstrapperApplicationHost. After installing one of the prerequisite Microsoft Windows Installer 4.5 I forcefully reboot the PC (Windows XP) using: <ExitCode Behavior="forceReboot"/> The Bundle chain looks like this: <Chain> <PackageGroupRef Id="WindowsInstaller45"/> <PackageGroupRef Id="Netfx2Full"/> <PackageGroupRef Id="Netfx4Full"/> <PackageGroupRef Id="CustomPkg"/> <PackageGroupRef Id="SQLExpress"/> </Chain> After it reboots, I want my installation to continue after that, but it actually detects the installation and shows Uninstall option.

How do I detect the currently installed features during a MajorUpgrade using WiX Burn MBA Bundles?

﹥>﹥吖頭↗ 提交于 2019-11-30 18:48:24
I'm using WiX 3.7's Burn/Managed Bootstrapper Application features to create a custom MBA-based installer. For each of the packages in my bundle's chain, when performing a MinorUpdate, I can easily detect which of the package features are already installed to ensure I maintain those feature selections during the upgrade by using these events provided in the WiX base class for the bootstrapper: DetectPackageComplete , DetectMsiFeature , DetectRelatedBundle , DetectRelatedMsiPackage , DetectComplete . However, during a MajorUpgrade, I'm only seeing a way to determine which package(s) are

WiX Burn after restart/force reboot continuing installation

戏子无情 提交于 2019-11-30 17:08:25
问题 I have a WiX Burn custom installer using ManagedBootstrapperApplicationHost. After installing one of the prerequisite Microsoft Windows Installer 4.5 I forcefully reboot the PC (Windows XP) using: <ExitCode Behavior="forceReboot"/> The Bundle chain looks like this: <Chain> <PackageGroupRef Id="WindowsInstaller45"/> <PackageGroupRef Id="Netfx2Full"/> <PackageGroupRef Id="Netfx4Full"/> <PackageGroupRef Id="CustomPkg"/> <PackageGroupRef Id="SQLExpress"/> </Chain> After it reboots, I want my

How do I detect the currently installed features during a MajorUpgrade using WiX Burn MBA Bundles?

三世轮回 提交于 2019-11-30 03:23:57
问题 I'm using WiX 3.7's Burn/Managed Bootstrapper Application features to create a custom MBA-based installer. For each of the packages in my bundle's chain, when performing a MinorUpdate, I can easily detect which of the package features are already installed to ensure I maintain those feature selections during the upgrade by using these events provided in the WiX base class for the bootstrapper: DetectPackageComplete , DetectMsiFeature , DetectRelatedBundle , DetectRelatedMsiPackage ,

How to create a bootstrapper application without a license agreement step

左心房为你撑大大i 提交于 2019-11-29 22:48:01
I have created a WiX Bootstrapper project. When the installation runs, it presents a license agreement. I want to create a bootstrapper without this step as I don't want it to show any license agreement. Is it possible to do it? If yes, how? Assuming that you are using the WiX Standard Bootstrapper Application, your current BootstrapperApplicationRef might look like this: <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense" /> WixStandardBootstrapperApplication has three variants as explained in the docs . HyperlinkLicense is the simplest. It has a license link on the

Make WIX installer place files in AppData

a 夏天 提交于 2019-11-29 16:57:30
I'm writing a dapp for ethereum client for windows. In order to make dapp available for user I have to place specific files in the folder in appdata. So I just should place some files in %appdata%\Parity\Ethereum\dapps\mydappname . But I always get weird errors with WIX, the last one is Error 93 ICE64: The directory dapp is in the user profile but is not listed in the RemoveFile table. I have following myapp.wixproj <?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="4.0" DefaultTargets="Build" InitialTargets="EnsureWixToolsetInstalled" xmlns="http://schemas.microsoft.com/developer

Unable to uninstall the application which is installed using wix installer

自古美人都是妖i 提交于 2019-11-29 16:50:41
I have used wix installer to create an installer for my c# application. Installation happened fine, but I am not able to uninstall the application. I see below the logs MSI (s) (78:AC) [15:32:06:199]: Machine policy value 'Debug' is 0 MSI (s) (78:AC) [15:32:06:199]: ******* RunEngine: ******* Product: C:\wix\Installer\\bin\Debug\MyService-Debug-x86.msi ******* Action: ******* CommandLine: ********** MSI (s) (78:AC) [15:32:06:207]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (78:AC) [15:32:06:326]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038 MSI (s

Wix custom uninstallation action - how to run before msi removing files

若如初见. 提交于 2019-11-28 14:00:39
I have a custom action that adds files to the installation directory. When the program is being uninstalled, another custom action tries to remove those files, so that the installation directory can be deleted. The problem is that my custom uninstallation action runs after the removal of standard install files, so the installation directory is left there, although it's empty. The config looks similar to this: <CustomAction Id="AddFilesAction" BinaryKey="installerActions" DllEntry="AddFiles" Execute="deferred" Return="check" Impersonate="no" /> <CustomAction Id="CleanupAction" BinaryKey=