wix3.6

wix service dependencies

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-01 17:56:22
My product has several features including two services. Let's call them ServiceA and ServiceB. Both of these service features are optional. However if both ServiceA and ServiceB is selected during install I want to create a service dependency between them so that ServiceB will depend on ServiceA (in other words ServiceB must always start before ServiceA is launched). How do I achieve this in WIX 3.6? Natalie Carr <ServiceInstall Id="ServiceA" DisplayName="ServiceA" Name="ServiceA" Account="LocalSystem" Start="auto" ErrorControl="normal" Type="ownProcess"> <ServiceDependency Id="ServiceB"/> <

wix service dependencies

a 夏天 提交于 2019-12-01 17:55:40
问题 My product has several features including two services. Let's call them ServiceA and ServiceB. Both of these service features are optional. However if both ServiceA and ServiceB is selected during install I want to create a service dependency between them so that ServiceB will depend on ServiceA (in other words ServiceB must always start before ServiceA is launched). How do I achieve this in WIX 3.6? 回答1: <ServiceInstall Id="ServiceA" DisplayName="ServiceA" Name="ServiceA" Account=

How to fix ICE57.Per-User installation

天大地大妈咪最大 提交于 2019-12-01 17:25:02
Our application writes some settings to the registry into the HKCU hive during runtime. I want to delete this settings during uninstall. Here is code: <Fragment> <DirectoryRef Id="INSTALLLOCATION" DiskId="1" FileSource="$(var.SourceDirProject)\"> <Component Id="DeleteHkcuManufacturerHive" Guid="GUID"> <Condition>REMOVE="ALL" AND NOT UPGRADINGPRODUCTCODE</Condition> <CreateFolder/> <RemoveRegistryKey Action="removeOnUninstall" Id="HKCUkey" Root="HKCU" Key="Software\$(var.Manufacturer)"/> </Component> </DirectoryRef> </Fragment> ICE57: Component 'DeleteHkcuManufacturerHive' has both per-user and

How to fix ICE57.Per-User installation

拟墨画扇 提交于 2019-12-01 16:53:47
问题 Our application writes some settings to the registry into the HKCU hive during runtime. I want to delete this settings during uninstall. Here is code: <Fragment> <DirectoryRef Id="INSTALLLOCATION" DiskId="1" FileSource="$(var.SourceDirProject)\"> <Component Id="DeleteHkcuManufacturerHive" Guid="GUID"> <Condition>REMOVE="ALL" AND NOT UPGRADINGPRODUCTCODE</Condition> <CreateFolder/> <RemoveRegistryKey Action="removeOnUninstall" Id="HKCUkey" Root="HKCU" Key="Software\$(var.Manufacturer)"/> <

wix bootstrapper

冷暖自知 提交于 2019-12-01 13:42:11
I have written a managed wix bootstrapper using WPF. The actual installation steps requires chaining of multiple msi's/exe's and batch files. <Chain> <MsiPackage SourceFile="xxx"/> <ExePackage Id="Test" SourceFile="..\TestBatch.bat" Vital="yes"/> <MsiPackage SourceFile="yyy"/> </Chain> During the execution of each package, a message should be displayed (preferably from the bootstrapper UI) indicating which msi/exe package/ batch file is being executed currently. In short, a ProgressText is needed in the bootstrapper How can I make this happen? Another question: I do not want all the msi's to

How can I continue the installation from the point it left due to reboot?

£可爱£侵袭症+ 提交于 2019-12-01 12:50:28
How can I continue my installer after it reboots during installation of some package? Actually, I have build an installer package of a project using WiX bundles (having different packages to install in a chain). But when it installs Microsoft Windows Installer 4.5 (.msi) it goes to reboot the PC. After it reboots, I want my installation to continue after that. How can I do that? I guess we can do it with the use of the exit code, but I don't know how to use it in WiX bundles. caveman_dick Yes, you are right. You need to use an exit code in the Bundle: <ExePackage Id="WinXP_x86" Cache="no"

wix bootstrapper

▼魔方 西西 提交于 2019-12-01 11:51:18
问题 I have written a managed wix bootstrapper using WPF. The actual installation steps requires chaining of multiple msi's/exe's and batch files. <Chain> <MsiPackage SourceFile="xxx"/> <ExePackage Id="Test" SourceFile="..\TestBatch.bat" Vital="yes"/> <MsiPackage SourceFile="yyy"/> </Chain> During the execution of each package, a message should be displayed (preferably from the bootstrapper UI) indicating which msi/exe package/ batch file is being executed currently. In short, a ProgressText is

Wix project template for Visual Studio Express versions?

大憨熊 提交于 2019-12-01 09:20:11
Is it possible to use Wix with Express editions? I am interested in 2010/2012 versions. I know I can use candle and light from the command line, but I am interested in integration with IDE The Express versions of VS does not allow to extend the VS with the necessary plug-ins. So you have to stay with the command line. Alternatively to VS you could try WiXEdit. Actually, if the goal is to have a free installer suite, WiX is perfectly happy installing into Visual Studio Shell Integrated , which is freely available. All features of WiX are available. The only limitation is you have to open a

Wix project template for Visual Studio Express versions?

旧时模样 提交于 2019-12-01 06:16:22
问题 Is it possible to use Wix with Express editions? I am interested in 2010/2012 versions. I know I can use candle and light from the command line, but I am interested in integration with IDE 回答1: The Express versions of VS does not allow to extend the VS with the necessary plug-ins. So you have to stay with the command line. Alternatively to VS you could try WiXEdit. 回答2: Actually, if the goal is to have a free installer suite, WiX is perfectly happy installing into Visual Studio Shell

WiX XmlConfig: Purpose for nesting XmlConfig in XmlConfig

青春壹個敷衍的年華 提交于 2019-12-01 04:43:40
What is the purpose and/or gain (other than increased readability for creating/deleting attributes) to nesting an XmlConfig element in another XmlConfig element? Example of what I'm referring to (I'm using WiX 3.6 ): <util:XmlConfig ...> <util:XmlConfig ... /> </util:XmlConfig> The short answer: the only purpose of the option to have nested <util:XmlConfig> elements is to be able to add/remove attributes to/from the newly created elements in a more readable way. So, this is basically what you assumed. Consider the following initial XML file: <?xml version="1.0" encoding="utf-8"?> <cars> <car