wix

问题 I've started playing with Managed Boostrapper Classes and events. Making story short, I've added BoostrapperCore.dll and it would give you the namespace Microsoft.Tools.WindowsInstallerXml.Bootstrapper I was able to get some info from some examples present in different blogs. For instance, the Entry point is BootstrapperApplication.Run() , is called when bootstrapper application is ready to run. Then there are events like: BoostrapperApplication.DetectBegin BoostrapperApplication

问题 I have a file that has a 32bit version and a 64bit version. If I install my application on a 32bit machine, I want the 32bit version of the file to be installed. Likewise, the 64bit version should get installed if the installation is run on a 64bit machine. How do I check which type of machine the installer is being run on with WiX? Please, no one-line answers. I'm looking for specific WiX tags and where to put them in my WiX script. 回答1: You could probably just do two separate components,

问题 I am trying to make a installer for a printer driver, Using WIX I have some Dlls a *.cat file a *.gdp file an *.inf file I was thinking about using the INF to deploy the driver but don't know how to implement it. I sow this Question too,(possibly duplicates) but as a beginner i could't completely understand how to do it. Am i need to copy those DLLs and other files to the relevant folders by my self and Write Registry. Or is their any easy way to use INF file to do the task by WIX's engine?

问题 Currently I have customised the Wix_InstallDirDlg to enable the user to set a registry key on install. There is a custom dialog that is shown after both the InstallDirDlg and the MaintenanceTypeDlg so that it caters for both install and repair scenarios. The custom dialog has a single textbox that is linked to a property. This property has a registry search so that if the user repairs or upgrades the previous value is preserved and therefore shown in the custom dialog for the user to validate

问题 We're evaluating if the Wix installer will be suitable for us in a project. The end user need to be able to install our software without admin rights. The installer needs to work with at least XP/Vista/Windows 7 without admin rights or UAC. I have a hard time finding good documentation and tutorials how this can be done. I have found a couple of old ones but they don't compile with candle/light with the latest Wix version. Does anyone have good examples or tutorials that might help? Thanks in

问题 An installer I have created with WiX installs a DLL using the SystemFolder variable, as well as a C# app into another folder. I want to directly reference the DLL from the app. Do I need to look up registry keys to find where the SystemFolder is? 回答1: No, you don't need to query the registry. Windows Installer has a series of built-in properties that automatically resolve to special well known locations such as SystemFolder. See System Folder Properties for more general information. For WiX,

问题 An installer I have created with WiX installs a DLL using the SystemFolder variable, as well as a C# app into another folder. I want to directly reference the DLL from the app. Do I need to look up registry keys to find where the SystemFolder is? 回答1: No, you don't need to query the registry. Windows Installer has a series of built-in properties that automatically resolve to special well known locations such as SystemFolder. See System Folder Properties for more general information. For WiX,

问题 I am trying to create multiple shortcuts to my application that pass different arguments on the commandline by using the Arguments attribute of the Shortcut element. I want to be able to reference an existing property from another property in my WiX file. I want to be able to create a shortcut by referencing the ARGUMENTS property via: <Component Id="MyAppProgramMenuShortcut" Guid="MY-GUID-HERE"> <RegistryValue Root="HKCU" Key="Software\[Manufacturer]\[ProductName]\MyAppShortcut" Type="string

问题 This is an installer for a SQL database. It really does not change anything on the local computer but connects to a database to make changes. The user could be upgrading 3 different database servers from one computer so they should be able to run it 3 times utilizing the same dialogs. I would like the installer to always show the same custom dialogs I have setup. I do not want it to go into the maintenance dialog. I have set the MajorUpgrade tag as so, which the documentation says covers

问题 I am using the windows installer to install/upgrade an installation. Using Visual Studio I can manually change the version number and then select yes when asked to change the ProductCode. This creates an installer that is capable of overwriting the existing installation provided that the following properties are set on the installer project RemovePreviousVersions True DetectNewerInstalledVersion True Now in my build server I can change the version number to the appropriate new version in the