wix

问题 I have created a setupkit with no UI using Wix for my application (called "XYZ" here). If I double click the MSI while XYZ.exe is runnning, it notifies me that a process is locking a file: I can choose to kill the locking process or I can abort the installation. This is fine: as a user I can decide what to do. But when I run the same MSI from the commandline, msiexec /i XYZ.msi /quiet /norestart if XYZ.exe is found running it will be killed. This is absolutely inacceptable in my scenario: the

问题 I am trying to add my own help file to Visual Studio 2010's Help Library by using WiX to run the HelpLibraryManagerLauncher that the Sandcastle Help File Builder creates after it builds my Sandcastle project. I am using WiX's QuietExec custom action to run the following command: HelpLibraryManagerLauncher.exe /product "VS" /version "100" /locale en-us /silent /brandingPackage Dev10.mshc /sourceMedia MyClassLibraryHelp.msha However, the MSI installer fails with the following: Action 00:00:00:

问题 I'm using wix3 to build a setup file, I would like to know whether the outlook is running during the installation. If the outlook is still running, the setup should notify the users to close it or have to reboot after the installation. I noticed that there is a feature can send a message to close the outlook directly, but that's not very friendly. I would like to knwo whether the FileInUse dialog can be called in such situation. Thanks. 来源： https://stackoverflow.com/questions/1335260/how-to

问题 I use Wix Toolset v3.11 to generate an .msi installer for my Windows application. How can I have a publisher name appear in the entry for my application in Settings -> Apps & features ? I noticed that some entries in that list include a publisher name underneath the app name: I set <Product ... Manufacturer="My Company Name" ... in my .wxs file and I can see this is stored in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\<guid>\Publisher .

问题 I might be suffering from a case of Sometimers Disease, but I could have sworn the last time I dipped my toe in WiX, it was recommended to have a seperate file for setting properties to be referenced later if any of those properties aren't meant to be static. Basically, updating them before the build sequence begins as-needed. So basically, I'm trying to: Load the Properties file into the WiX project (done) Create a WiX Property equal to one of the properties from that Properties file

问题 I'm using HEAT to auto generate WiX fragments for a directory of files. When the --.wxs file creating, why it include some unnecessary tags within the component? like follows scenario 1 <Component Id="cmpFF03591E2D2B9B2AA2AA444299A693DB" Directory="dir7307A6085BD4ABD9B8955C093FD541F5" Guid="*"> <Class Id="{00AB5D3B-4FAB-35AB-8916-59EE0247EFF1}" Context="InprocServer32" Description="Microsoft.Practices.EnterpriseLibrary.Common.Configuration.FileConfigurationSourceElement" ThreadingModel="both"

问题 Seems like I'm forever asking questions about Wix. This should be the last, and it's just a polishing one. I'm wanting my associated files to have an icon to go with them, but in my ProgId element, the advertise is not specified which I assume defaults to no. Therefore in the wix documentation, it states: For an advertised ProgId, the Id of an Icon element. For a non-advertised ProgId, this is the Id of a file containing an icon resource. I'm not understanding how this works at all. Do I set

问题 I've built an installer with WIX and have packaged it with the .NET 4.0 framework using the GenerateBootstrapper task. Now .NET 4.0 cannot be installed on XP SP2, but it appears to have no precondition check for this so its installer fails halfway through. I'd like to add my own check to make sure the OS that the entire package is being installed on is supported by the .NET 4.0 framework. Is there a way to embed an OS/Service Pack check in the bootstrapper when you use GenerateBootstrapper ?

问题 I'm having trouble getting a burn bundle with a custom managed bootstrapper application to launch on certain platforms that do not come with Windows Imaging Component, which is required to install .NET 4.0 (Windows 2003 being one of them). We are using the standard method of defining what the managed bootstrapper application requires: <WixVariable Id="WixMbaPrereqPackageId" Value="Netfx4Full"/> When this bootstrapper is run on a newly installed Windows 2003 R2 machine, it launches the

问题 How can I have Burn detect that the required .NET 4.5 framework is installed and if not notify the user prior to launching my custom UI that the install requires .NET 4.5 to run? Without the prerequisite check my custom UI (BootStrapperApplication) will fail to load. I do not want to install only prompt that it is missing. 回答1: In your Bundle.wxs file (or where ever you have the <Bundle> defined), add this: <bal:Condition Message="Add your message here">NETFRAMEWORK40FULL</bal:Condition> For