wix3.5 | 易学教程

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

Custom Action in C# used via WiX fails with error 1154

阅读更多关于 Custom Action in C# used via WiX fails with error 1154

问题 I am using WiX 3.5.1930 in Visual Studio 2010, targeting the .NET Framework 3.5. (Later weekly builds of WiX seem to be very broken with respect to their custom action template, at least for now. 1930 is the most recent build that seems to make a buildable C# CA with working references.) I have two custom action assemblies written in C#. One of them works fine. The other fails with the following error: CustomActionnNameHere returned actual error code 1154 (note this may not be 100% accurate

Wix Interactions with Conditions, Properties & Custom Actions

阅读更多关于 Wix Interactions with Conditions, Properties & Custom Actions

I am having a problem with a setting the enabled state of a button on a Dialog. The button in question is defined as: <Control Id="Next" Type="PushButton" X="236" Y="243" Width="56" Height="17" Default="yes" Text="!(loc.WixUINext)"> <Condition Action="disable">Validated = 0</Condition> <Condition Action="enable"><![CDATA[Validated <> 0]]></Condition> <Publish Event="EndDialog" Value="Return">1</Publish> </Control> The property Validated starts out at an initial value of 0, and as expected the next button starts out disabled. <Property Id="Validated" Value="0"/> The property itself is modified

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. 回答1: I found what it was that solves my issue. In

How to run heat.exe and register a dll in wix

阅读更多关于 How to run heat.exe and register a dll in wix

问题 I need to register a dll in regAsm and now i was using <CustomAction Id='comReg' Directory='INSTALLLOCATION' ExeCommand='"[WindowsFolder]Microsoft.NET\Framework\v4.0.30319\regasm.exe" "[INSTALLLOCATION]myProduct.dll" /codebase' Return='check' /> to register and to unregister <CustomAction Id='comUnreg' Directory='INSTALLLOCATION' ExeCommand='"[WindowsFolder]Microsoft.NET\Framework\v4.0.30319\regasm.exe" /u "[INSTALLLOCATION]myProduct.dll" /codebase' Return='check' /> Am using it and sometimes

Wix Interactions with Conditions, Properties & Custom Actions

阅读更多关于 Wix Interactions with Conditions, Properties & Custom Actions

问题 I am having a problem with a setting the enabled state of a button on a Dialog. The button in question is defined as: <Control Id=\"Next\" Type=\"PushButton\" X=\"236\" Y=\"243\" Width=\"56\" Height=\"17\" Default=\"yes\" Text=\"!(loc.WixUINext)\"> <Condition Action=\"disable\">Validated = 0</Condition> <Condition Action=\"enable\"><![CDATA[Validated <> 0]]></Condition> <Publish Event=\"EndDialog\" Value=\"Return\">1</Publish> </Control> The property Validated starts out at an initial value

How to pass CustomActionData to a CustomAction using WiX?

阅读更多关于 How to pass CustomActionData to a CustomAction using WiX?

How are properties set on CustomActionData to be retrieved by a deferred custom action? Ayo I Deferred custom actions can not directly access installer properties ( reference ). In fact, only CustomActionData property session.CustomActionData and other methods and properties listed here are available on the session object. Therefore, for a deferred custom action to retrieve a property such as the INSTALLLOCATION , you have to use a type 51 custom action — i.e. a set-property custom action — to pass that information along and you'll consume the data from the CustomAction's C# code through

How to pass CustomActionData to a CustomAction using WiX?

阅读更多关于 How to pass CustomActionData to a CustomAction using WiX?

问题 How are properties set on CustomActionData to be retrieved by a deferred custom action? 回答1: Deferred custom actions can not directly access installer properties (reference). In fact, only CustomActionData property session.CustomActionData and other methods and properties listed here are available on the session object. Therefore, for a deferred custom action to retrieve a property such as the INSTALLLOCATION , you have to use a type 51 custom action — i.e. a set-property custom action — to

WiX tricks and tips

阅读更多关于 WiX tricks and tips

问题 We\'ve been using WiX for a while now, and despite the usual gripes about ease of use, it\'s going reasonably well. What I\'m looking for is useful advice regarding: Setting up a WiX project (layout, references, file patterns) Integrating WiX into solutions, and build/release processes Configuring installers for new installations and upgrades Any good WiX hacks you\'d like to share 回答1: Keep variables in a separate wxi include file. Enables re-use, variables are faster to find and (if needed)