wix

问题 I've inherited a project that uses WIX Toolset (3.10.3) to build the installation package. The application downloads and stores shared data in c:\ProgramData\Vendor\ApplicationName . This path is however not created during the installation, but rather during the execution of the application itself, whenever the path is requested for the first time. I've now discovered a permissions related problem that occurs when multiple Windows users uses the application. Whenever the application downloads

问题 I am writing a WXS file for a package I want to install. For the sake of simplicity, let's say I want to install 1 file and then I want to execute a command against it (in my case, it is a public GPG key and I want to import it after the installation is done). Here are the relevant parts of my WXS file: <CustomAction Id="ImportKey" Directory="INSTALLDIR" ExeCommand="[SystemFolder]cmd.exe /C gpg --import keyfile.key" Return="check" /> <!-- Install file keyfile.key into C:\GnuPG --> <Directory

问题 I am writing a WXS file for a package I want to install. For the sake of simplicity, let's say I want to install 1 file and then I want to execute a command against it (in my case, it is a public GPG key and I want to import it after the installation is done). Here are the relevant parts of my WXS file: <CustomAction Id="ImportKey" Directory="INSTALLDIR" ExeCommand="[SystemFolder]cmd.exe /C gpg --import keyfile.key" Return="check" /> <!-- Install file keyfile.key into C:\GnuPG --> <Directory

问题 I am writing a WXS file for a package I want to install. For the sake of simplicity, let's say I want to install 1 file and then I want to execute a command against it (in my case, it is a public GPG key and I want to import it after the installation is done). Here are the relevant parts of my WXS file: <CustomAction Id="ImportKey" Directory="INSTALLDIR" ExeCommand="[SystemFolder]cmd.exe /C gpg --import keyfile.key" Return="check" /> <!-- Install file keyfile.key into C:\GnuPG --> <Directory

问题 I would like to be able to set the ALLUSERS property to either blank for current user or 1 for all users using two radio buttons placed in the 'Destination Folder' dialog. I understand that this is the code to run for current user: <Property Id="AllUSERS" Value="{}"/> and for all users: <Property Id="AllUSERS" Value="1"/> I've got this code to create the custom radio buttons: <Control Id="RadioButtonGroupID" Type="RadioButtonGroup" X="30" Y="94" Width="305" Height="100" Property="

问题 I would like to be able to set the ALLUSERS property to either blank for current user or 1 for all users using two radio buttons placed in the 'Destination Folder' dialog. I understand that this is the code to run for current user: <Property Id="AllUSERS" Value="{}"/> and for all users: <Property Id="AllUSERS" Value="1"/> I've got this code to create the custom radio buttons: <Control Id="RadioButtonGroupID" Type="RadioButtonGroup" X="30" Y="94" Width="305" Height="100" Property="

问题 Is it possible to include C++ code inside a Wix Project. For example either 1. Have C++ inside a file with extension ".wxs" (Wix source file) 2. Or Create ".cpp" file inside the Wix project and run it from Wix. ( I tried this, but Visual Studio doesn't allow me to create .cpp file in the project ... but only wxs & wsi files ) 回答1: No, you cannot directly include C++ Code/File in WIX project. You can write your own C++ Custom Action and then call it from your wix project. NOTE You should not

问题 I'm writing a WIX script. I have a custom-action that adds rows dynamically to the Registry table: function AddRegistry() { var registryView = Session.Database.OpenView("SELECT * FROM Registry"); registryView.Execute(); var record = Session.Installer.CreateRecord(6); record.StringData(1) = "Unique123456"; record.IntegerData(2) = 2; record.StringData(3) = "Software"; record.StringData(4) = "my_registry_string"; record.StringData(5) = "value"; record.StringData(6) = "MyComponent"; registryView

问题 Due to user confusion, our app requires separate installers for 32-bit and 64-bit versions of Windows. While the 32-bit installer runs fine on win64, it has the potential to create support headaches and we would like to prevent this from happening. I want to prevent the 32-bit MSI installer from running on 64-bit Windows machines. To that end I have the following condition: <Condition Message="You are attempting to run the 32-bit installer on a 64-bit version of Windows."> <![CDATA[Msix64 AND

问题 Due to user confusion, our app requires separate installers for 32-bit and 64-bit versions of Windows. While the 32-bit installer runs fine on win64, it has the potential to create support headaches and we would like to prevent this from happening. I want to prevent the 32-bit MSI installer from running on 64-bit Windows machines. To that end I have the following condition: <Condition Message="You are attempting to run the 32-bit installer on a 64-bit version of Windows."> <![CDATA[Msix64 AND