wix

问题 Since the default language for the WiX installler UI is english, I'd like to change to another langue like german or something. I'm sure the must be some predefined langue packs, coming with the toolkit? Is there a way can I change the language of the WiXs default installer UI? (I am using the Visual Studio (2012) Addin) 回答1: You can simply add a parameter to the WiX linker ( light.exe ): -cultures:culture-code You can find all culture codes here. When using Viual Studio simply open the

问题 I am newbie to Wix and creating a multi feature Wix project. Our product is having 4 modules and each module has to be included as a feature in the Windows installer. But all features are sharing the same folder structure. I am using commandline to build my Wix project. After harvesting every module into different wxs fragments, the light.exe giving error saying that duplicate id in the dirercoty table. My file tree is look like... ModuleA - Core |--bin |--etc | |--mgr |--lib |-- a.txt

问题 I install my application to a specific folder using the below wxs code: <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="ProgramFilesFolder"> <Directory Id="INSTALLDIR" Name="CompanyName"> <Directory Id="SUBDIR" Name="Application Launcher"> <Component Id="ApplicationFiles" Guid="*"> <File Name="app.exe" Id="AppFile1" Source="app.exe" Vital="yes" /> </Component> </Directory> </Directory> </Directory> </Directory> I want to specify the installation folder with a parameter to be given

问题 Background information: We used to have a Visual Studio 2010 based installer project, but our install situation got a lot more complicated, and with the projects going away anyway in 2012, we figured we'd start learning WiX / InstallShield LE. The Problem: InstallShield LE seems far too limited in the MSI files it creates to fit our needs -- (example, if you check the Office 2007 prerequisite, even though the error says you need "Office 2007 or later" it will fail if you have Office 2010

问题 This seems like it should be intuitive, but so far its been anything but. How do I simply set a property I have defined in my product.wxs when my custom dialog first opens? My Property is called "Port" which is initialized as blank. I have another called "df_Port", which I set to "8080". (These are set in my Product.wxs) When my Custom Dialog opens I want to set "Port" to "df_Port". I also have an Edit control on the dialog whose "Property" setting is set to "Port". So obviously the User

问题 I am trying to register an out-of-process COM file (.exe) through WiX after extracting the COM registration from regspy.exe, and am running into the problem that the registry key I need to write is: <RegistryValue Value="C:\PROGRA~1\COMMON~1\file.exe /Automation" Type="String" /> Now I would like to use the Windows Installer property [CommonFilesFolder] as not everyone installs to C:\ For an in-process (.dll) the long name is acceptable: <RegistryValue Value="[CommonFilesFolder]file.dll" Type

问题 Now I use something like this: <Component Id="RegistryEntries" Guid="<guid>" KeyPath="yes"> <RegistryKey Root="HKCU" Key="<path>" Action="createAndRemoveOnUninstall"> <RegistryValue Name="myStrings" Action="append" Type="multiString"> 1 </RegistryValue> <RegistryValue Name="myStrings" Action="append" Type="multiString"> 2 </RegistryValue> <RegistryValue Name="myStrings" Action="append" Type="multiString"> 3 </RegistryValue> <RegistryValue Name="myString" Value="x" Type="string"/> <

问题 I'm using the Wix HeatFile task in a post build step <HeatFile OutputFile="Interop.dll.wxs" File="..\Interop\bin\x86\$(Configuration)\Interop.dll" DirectoryRefId="INSTALLDIR" ComponentGroupName="Interop_Dll" AutogenerateGuids="true" SuppressFragments="true" SuppressRootDirectory="true" ToolPath="$(WixToolPath)" PreprocessorVariable="var.InteropBinDir" /> Once I do a build, it locks my dll and subsequent builds fail with: Error 6 Unable to copy file "obj\x86\Debug\Interop.dll" to "bin\x86

问题 I installed an test application which has two features (FirstFeature & SecondFeature). I want to remove only one feature (SecondFeature) from the application. I tried using REMOVE property in command line. Here is the command used to remove SecondFeature. msiexec /x RemoveFeatures.msi REMOVE="SecondFeature" /L*V log.LOG But it is uninstalling the complete application. Log file shows that REMOVE=ALL is added by default. Here is the log file details. MSI (s) (24:B4) [17:39:05:231]: Command Line

问题 Our product has an MSI installer (written in WiX) which basically copies some files into a folder c:\ourproduct and installs a windows service "ourwindowsservice". We'd like to add support for multiple instances of the service, and it should be possible to install/uninstall them independently of each other. Similar e.g. to SQL Server, each instance should have a name which can be passed to the MSI as a command line parameter. Example: instance "A" => copy files to "c:\ourproductA", install