wix3.6

Installed program not visible to all users

戏子无情 提交于 2019-12-13 00:36:05
问题 I am using wix setup to install some package. When I install it, it appears in "Programs and Features" in control panel. It is visible to some users not all, and they can uninstall it as well. Problem is when the other user who can not see what I installed in control panel, when he installs something I can't see it. I can install the same package again and it won't complain that it already exists. 回答1: MSI packages are installed per-user or per-machine. Only per-machine products are

Burn: How to store a checkbox value in a variable

本秂侑毒 提交于 2019-12-12 21:02:10
问题 I was wondering how you store a checkbox value in a variable? I am using WiX Burn with a custom RtfTheme. For example: RtfTheme.xml <Checkbox Name="TestCheckbox" X="-11" Y="-51" Width="246" Height="17" TabStop="yes" FontId="3" HideWhenDisabled="yes">Please select this box</Checkbox> Bundle.wxs <Variable Name="TestVariable" Type="numeric" Value="![CDATA[TestCheckbox]]"/> I want the value of "TestVariable" to change value whenever I select or deselect the checkbox. Any help? 回答1: WixStdBA

How to use MajorUpgrade and RemoveFeatures to remove only specific features and still un-install the previous version of the product

强颜欢笑 提交于 2019-12-12 09:42:23
问题 I swapped to Wix 3.6 from the Microsoft Installer that was packaged with VS 2010. I am trying to release a seamless upgrade to our users by using the <MajorUpgrade/> Tag, however I have one feature that I do not want to be un-installed while performing this major upgrade. As seen below I have RemoveFeatures="[ProductFeature]" which will result in only the ProductFeature being removed and the DataFeature will remain, but this results in the entry not being removed from the "Programs and

Heat.exe: 64-bit .dll fails to be converted to a 64-bit .msi

拟墨画扇 提交于 2019-12-12 04:50:57
问题 I tried to generate a 64-bit FireBreath MSI installer using heat.exe but got the following output: heat.exe : warning HEAT1108 : The command line switch 't:' is deprecated. Please use 't' instead. heat.exe : warning HEAT5150 : Could not harvest data from a file that was expected to be a SelfReg DLL: C:\Users\firebreath-master\buildPlugin\bin\Release\myPlugin64.dll. If this file does not support SelfReg you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the

WIX Change the default Install Path

人走茶凉 提交于 2019-12-12 02:33:44
问题 I am trying to change the default install path to User's Home directory/ProductName. Below is my code(its not the entire code) <Package InstallerVersion="200" Compressed="yes" InstallScope="perUser" Description="desc" Comments="View Violations in APD" InstallPrivileges="elevated"/> <Property Id="WIXUI_INSTALLDIR" Value="INSTALLFOLDER"/> <Property Id="ENVIRONMENT" Secure="yes" /> <UIRef Id="WixUI_InstallDir" /> <UIRef Id="WixUI_ErrorProgressText" /> <Fragment> <DirectoryRef Id="INSTALLFOLDER">

WiX Custom Action - Pass file list

不问归期 提交于 2019-12-12 01:36:33
问题 I am preparing installation packages for a plugin which replace some files of other application. I need make a backup of that files, so I prepared CustomAction which will do that. How can I pass as argument to my custom action locations of all files which will be copied during installation? Do I need to make that list manually? 回答1: Instead of creating a custom action, why not use the WiX CopyFile element to back up those files. 回答2: You can pass parameters to custom actions by setting

WiX: CustomAction based on the outcome of another CustomAction

孤人 提交于 2019-12-11 15:15:32
问题 I am fairly new to WiX so may be I am asking something very straight forward but I couldn't find much help googling it. I want to perform 2 customActions, say, ca1 and ca2, where execution of ca2 depends on outcome of ca1, something like below: if ( ca1 == SUCCESS ) { Perform ca2 } So ca2 should only be executed if my ca1 returns success (doesnt fails). What is the easiest way to do this in WiX ? 回答1: What you describe is the default. If a custom action fails, the installation aborts, and

error LGHT0094 : The identifier 'CustomAction:WixUIPrintEula' could not be found

那年仲夏 提交于 2019-12-11 14:58:25
问题 When I run the below command from the command line for the WIx installer after migrated from version 2.0 to 4.0: E:\Code\PCPE\builder>ant -v -f Build.xml -Dlabel =.001 install I am getting the below error. [exec] E:\Code\EMR\Wix\src\ui\LicenseAgreementDlg.wxs(34) : error LGHT0094 : The identifier 'CustomAction:WixUIPrintEula' could not be found. Ensure you have typed the reference correctly and that all the necessary inputs are provided to the linker. [ant] Exiting E:\Code\EMR\builder

Wix uninstall product using command line during installation

蓝咒 提交于 2019-12-11 11:50:01
问题 I made a Wix project that attemps to install a simple .txt example file. But, as a prerequisite, I want to uninstall a previous application. To do so, I know msiexec allows you to uninstall a product by simply writing: msiexec /x {PRODUCT_CODE} on a command line. Fortunately, I know this PRODUCT_CODE , so I tried to create a CustomAction to uninstall that product before the installation starts, like this: <CustomAction Id="PropertyAssign" Property="SilentLaunch" Value="msiexec.exe /x

wix generating new upgrade code

匆匆过客 提交于 2019-12-11 08:25:20
问题 My project needs to have the ability to install 2 versions or more simultaneously. as far as i can find, the solution i have found is changing the upgrade code for each build of the installer. however i want to do this automatically. in regular GUID i just use "*" but this won't work for upgradecode. is there a way to generate new upgradecode in every wix prebuild or any other solution? <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:util=