wix3 | 易学教程

How do I share a WiX fragment in two WiX projects?

阅读更多关于 How do I share a WiX fragment in two WiX projects?

We have a WiX fragment in a file SomeDialog.wxs that prompts the user for some information. It's referenced in another fragment in InstallerUI.wxs file that controls the dialog order. Of course, Product.wxs is our main file. Works great. Now I have a second Visual Studio 2008 Wix 3.0 Project for the .MSI of another application and it needs to ask the user for the same information. I can't seem to figure out the best way to share the file so that changing the information requested will result in both .MSIs getting the new behavior. I honestly can't tell if a merge module, an .wsi (include) or a

WiX Includes vs Fragments

阅读更多关于 WiX Includes vs Fragments

问题 What's the difference between a WiX include ( .wxi file) and a WiX fragment ( .wxs file)? What are the use cases for each? Which should be used and why? 回答1: The file extension is a convenience, the content of the file is what really matters. The distinction makes it easier to manage the difference between the actual installation (wxs files) and the properties required to create the installation (wxi files). For example, your wxs files specify the product and its contents (which files you

WIX, Dot Net managed custom Action, dynamically fill combo box with SQL Server instances, MSI

阅读更多关于 WIX, Dot Net managed custom Action, dynamically fill combo box with SQL Server instances, MSI

问题 In WIX am in-need of a dot net managed custom code to dynamically populate a combo box with the values of sql server instances in that network. I tried to google but got nothing worked Any help is greatly appreciated. 回答1: [CustomAction] public static ActionResult FillServerInstances(Session xiSession) { xiSession.Log("Begin CustomAction"); xiSession.Log("Opening view"); View lView = xiSession.Database.OpenView("DELETE FROM ComboBox WHERE ComboBox.Property='DBSRVR'"); lView.Execute(); lView =

TrustedInstaller is preventing registry writes to HKCR\DirectShow\MediaObjects\Categories

阅读更多关于 TrustedInstaller is preventing registry writes to HKCR\DirectShow\MediaObjects\Categories

问题 I'm trying to install a DMO which requires me to write to HKCR\DirectShow\MediaObjects\Categories\57f2db8b-e6bb-4513-9d43-dcd2a6593125 , this registry path is protected by TrustedInstaller and it seems that this protection is new in Windows 7 (it work on previous platforms). How am I suppose to install DMOs? There are plenty of places that suggest to take ownership on the this registry key but this just doesn't feel right. BTW, were using boilerplate Wix3 to write the registry values. 回答1:

Failed to open XML file - Wix unable to update appsettings.json

阅读更多关于 Failed to open XML file - Wix unable to update appsettings.json

问题 I am using Wix to create MSI installers. My requirement is to pass parameters while installing msi from the command line and update' the appsettings.json` with the values passed. To achieve this, I have added below property and component. <Property Id="ApplicationLog.pathFormat" /> <Component Id="config" Guid="*"> <File Id="appconfig" Source="$(var.BasePath)\appsettings.json" KeyPath="yes" Vital="yes"/> <util:XmlFile Id="_pathFormat_" File="$(var.BasePath)\appsettings.json" Action="setValue"

Is there a way to set a preprocessor variable to the value of a property?

阅读更多关于 Is there a way to set a preprocessor variable to the value of a property?

I have a WiX include file with the following code <Fragment Id="PropertyFragment"> <Property Id="DynamicLanguageCode" Value="[SystemLanguageID]" /> <?define productLanguage = [DynamicLanguageCode]?> </Fragment> Now in my Product tag in my WiX script I'd like to set the Language attribute to the value of productLanguage, as it only takes localizable integers. Is there a way I can get my variable to be assigned the value of the property? Thanks There seems to be confusion in your mind about what the difference is between wix variables and windows installer properties. A wix variable can be

Defining Wix properties and values based on VS active configuration

阅读更多关于 Defining Wix properties and values based on VS active configuration

问题 How can I define Wix properties and values that change depending on which Visual Studio configuration is active? e.g. For our release build, var x = 1 and for the export build, var x = 2. 回答1: We pass properties into WiX from the wixproj files using <DefineConstants>configuration=$(Configuration)</DefineConstants> In a PropertyGroups section. Then you can use them inside wix as $(var.configuration) <?if $(var.configuration) = Debug ?> <?define x=1 ?> <?endif ?> The WiX help file has a whole

Add a folder to installer in wix not files?

阅读更多关于 Add a folder to installer in wix not files?

My installer has to copy files into installdir... My application has around 2000 files and it is not possible for me to write the script to add each and every file to the installer. Is there any option in wix so that I can add all the files or the entire folder consisting the files at once? I am new to wix and i didnt find any option in any tutorial for this... Please do assist me and thanks in advance..... Heat is the WiX harvest tool . You can run it on a directory to generate the necessary WiX source code. EDIT: If you want to run heat before your VS project builds, add it to your project

Including all dependencies

阅读更多关于 Including all dependencies

问题 I'm just starting out with WiX as I need to be able to automate building an MSI on our CI server. Is there anyway to automatically include all the dependencies of a project? 回答1: The "proj" extension to heat.exe is getting better. Heat isn't quite ready to be used for production in an automated fashion. It's a very reasonable way to get the initial structure put together but doesn't quite do the right thing with repeated runs (for example, Component/@Guids aren't stable, yet...). When the

How to check for .net framework 4.7.1 with Wix 3.11

阅读更多关于 How to check for .net framework 4.7.1 with Wix 3.11

I am trying to check for .net Version with Wix 3.11 via Condition. This works fine until 4.5 like this: <PropertyRef Id="NETFRAMEWORK45" /> <Condition Message="This application requires .NET Framework 4.5. Please install the .NET Framework then run this installer again."> <![CDATA[Installed OR NETFRAMEWORK45]]> </Condition> Checking for anything above 4.5 seems not to be possible - at least not with this mechanism. How can I do that? Christopher Painter That method (PropertyRef) is syntactical sugar. The NetFxExtension preprocessor injects the implementation at compile time. WiX is currently