wix3.5 | 易学教程

How can I create a shortcut on the Users Desktop folder

阅读更多关于 How can I create a shortcut on the Users Desktop folder

问题 Updated with Complete Wix Project as per craigster <?xml version="1.0" encoding="UTF-8"?> <?define SourceDir = "C:\Users\BillSmith\Documents\Visual Studio 2015\Projects\AIS\AIS\bin\Debug" ?> <?define icon = "C:\Users\BillSmith\Documents\Visual Studio 2015\Projects\AIS\AIS\bin\Debug\1Password.ico" ?> <?define DesktopFolder = "H:\Desktop" ?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Product Id="*" Name="APS" Language="1033" Version="1.3.0.0" Manufacturer="SS" UpgradeCode="890c447c

Referencing a WixVariable defined in a WiX Library Project from a WiX Setup Project

阅读更多关于 Referencing a WixVariable defined in a WiX Library Project from a WiX Setup Project

I'm trying to configure a WiX setup and library so that the version of one of the files in the library is used as the Product/@Version in the setup. Background In a setup with the files defined locally this is relatively straightforward in that assuming the component project is referenced by the WiX project and then configured: <Component Id="Company.Assembly" Guid="[GUID]"> <File Id="Company.AssemblyFile" Name="Company.Assembly.dll" KeyPath="yes" DiskId="1" Source="$(var.Company.Assembly.TargetPath)" /> </Component> Then the product version can be set as <Product Id="[GUID]" Name="Product

Cannot register DLL using WiX

阅读更多关于 Cannot register DLL using WiX

问题 I am trying to register a DLL using WiX. Now I know and understand that I should use heat and get it to pull the registry information for me, but heat seems to fail with the following error message: heat.exe : warning HEAT5150 : Could not harvest data from a file that was expected to be a SelfReg DLL: C:\Users\seb\Desktop\Development\addin.dll. If this file does not support SelfReg you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Unable to load

Install features based on checkboxes

阅读更多关于 Install features based on checkboxes

I am trying to make it so that when the user selects something via check box, a corresponding feature will be installed. I am aware of the prebuilt feature tree that Wix provides but there are some other things that I am doing that do not allow me to use this function. I am curious as to how to link the two together so that when the user selects the check box "Install Feature X", feature X is installed when the user clicks the install button. I found what it was that solves my issue. In order to do as I had intended I needed to create a check box for each individual feature as so. <Control Id=

(WiX) Program files shortcut for per-machine install

阅读更多关于 (WiX) Program files shortcut for per-machine install

问题 Following the example here, I added a shortcut to the ProgramMenuFolder that launches my application. (My code is actually simpler because I don't need the extra folder.) <DirectoryRef Id='ProgramMenuFolder'> <Component Id='cmpStartMenuShortcut' Guid='MY GUID HERE'> <Shortcut Id='StartMenuShortcut' Name='$(var.ProductName)' Icon='MainIcon.ico' Description='$(var.ProductName)' Target='[ClientDir]myapp.exe' WorkingDirectory='ClientDir'/> <RegistryValue Action='write' Type='integer' Root='HKCU'

WiX installer fails with error code 2819

阅读更多关于 WiX installer fails with error code 2819

问题 I am trying to create an installer using WiX which doesn't show the license agreement at the start. But I get the error as below. This is the full Product.wxs file I have at the moment. It compiles and builds OK. Why am I getting an error like this? Is my Fragment section in the right place? I have removed the Publish elements pertaining to license and modified the welcome dialog's next button to show the install directory dialog instead of license agreement. This is as mentioned in the help

How do I make a WIX MSI always remove a previous version?

阅读更多关于 How do I make a WIX MSI always remove a previous version?

问题 I have CI build system builds an MSI whenever a developer checks in a change. We run automated acceptance tests on the installed MSI. Basically every MSI is a complete install of the product, so we don't have any versioning (ala Windows installer) per se.. Each MSI has the same product GUID and upgrade GUID, and the same version number. but has a different package GUID (use '*' in wix). What I want to achieve is that when the installer runs, it will 'uninstall' any previously installed

How to create a directory in wix?

阅读更多关于 How to create a directory in wix?

问题 My requirement is to create a directory in programdata/test/example . How can I do that in wix? 回答1: Define the folder like this: <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="CommonAppDataFolder"> <Directory Id="TestFolder" Name="test"> <Directory Id="ExampleFolder" Name="example" /> </Directory> </Directory> </Directory> The important part here is the CommonAppDataFolder Id, which is known by Windows installer. You can find the full list of known system folders in the Windows

Error 2896 using a WiX C#/.NET 4 custom action

阅读更多关于 Error 2896 using a WiX C#/.NET 4 custom action

问题 I am trying to use my first custom action in WiX and I get: error 2896: Executing action CustomActionTest failed. I am using Visual Studio 2010, WiX 3.5, 64-bit Windows 7 Ultimate, .NET Framework 4. Here are what I think are the relevant sections: <Binary Id="JudgeEditionCA" SourceFile="..\JudgeEditionCA\bin\Debug\JudgeEdition.CA.dll" /> <CustomAction Id="CustomActionTest" BinaryKey="JudgeEditionCA" DllEntry="CustomActionOne" Execute="immediate"/> <Control Id="Next" Type="PushButton" X="248"

How do I suppress ICE errors from merge modules

阅读更多关于 How do I suppress ICE errors from merge modules

问题 I build an installer using WiX 3.5. The installer utilizes VB6 merge modules. I always get a lot of error messages from light similar to this: error LGHT0204: ICE03: Table: Class Column: CLSID Missing specifications in _Validation Table (or Old Database) So, VB6 is obviously old and I should assume it's an Old Database. That's why I want to ignore the error messsage since I must be careful with the errors from my WiX source. When I pass -sw03 to candle and light the error messages are NOT