wix

问题 I'd like to read a value from an INI file in a WiX installer. I've just tried to use IniFileSearch, but this looks for an INI file or a path specified in an INI file (the documentation isn't clear), it doesn't read a value from an INI file. Do I need a customaction to do this? And if so, what would people suggest? Seems very strange if WiX doesn't have this, though! Code I'm using: <Property Id="SP"> <IniFileSearch Id="SearchSPVersion" Name="sp.ini" Section="ServicePack" Key="Version" Type=

问题 I'd like to read a value from an INI file in a WiX installer. I've just tried to use IniFileSearch, but this looks for an INI file or a path specified in an INI file (the documentation isn't clear), it doesn't read a value from an INI file. Do I need a customaction to do this? And if so, what would people suggest? Seems very strange if WiX doesn't have this, though! Code I'm using: <Property Id="SP"> <IniFileSearch Id="SearchSPVersion" Name="sp.ini" Section="ServicePack" Key="Version" Type=

问题 We are trying to build an installer, in Wix, for a product. Part of this product requires the installation of elasticsearch as a service, and getting it running as a service. The service should run under a separate user account. The first step, getting the user account set up, has been successful. However, in order to allow elasticsearch to run correctly, we need to set up certain Environment variables. In order to reduce the chance of inadvertent user error, we will have to have these

问题 I am trying to create a custom UI for WiX and Burn. I'm almost done except one thing. In the end of installation which is upgrading(for exaple 1.0.0 to 1.1.0) uninstall for the previous version starts and the UI of it shows. My question is how should I handle this so the user doesn't see uninstall UI in the end. 回答1: When performing an upgrade of a Burn-based installer, the process will upgrade each of the MSIs bundled inside the installer, then it will uninstall the previous version's bundle

问题 I have chained multiple Msi/exec packages in my Bundle.wxs. In my managed Bootstrapper code, I would like to get the parameters (such as DisplayName, Vital, etc) of the current package that is being executed. Right now, I have only found events that provide the packageID. Can I use this to somehow access other properties of the package? 回答1: Yes. A file called BootstrapperApplicationData.xml is created during the build process and included with your Bootstrapper Application. The

问题 I have a command line I want to run during the install of a merge module (created by WiX) with the below code. <CustomAction Id='SetWebsiteProtocols' Execute='commit' Return='ignore' Impersonate="yes" FileKey='Web.config' ExeCommand='c:\windows\system32\inetsrv\appcmd.exe set app "Default Web Site/My Website" /enabledProtocols:http,net.tcp,net.pipe' /> <InstallExecuteSequence> <Custom Action="SetWebsiteProtocols" After="InstallFiles"/> </InstallExecuteSequence> When I run the command on the

问题 in a wix burn bootstrapper bundle : how to detect whether ms vcredist 2013 x86 is present or not? i'm doing a check for the Upgrade Id / UpgradeCode of that particular package, but the bundle always installs it afresh, even though it is installed already. ... <Bundle> ... <Chain> <!-- redist packages --> <PackageGroupRef Id="redist"/> ... </Chain> </Bundle> <Fragment> <PackageGroup Id="redist"> <PackageGroupRef Id="redist_vc120" /> ... </PackageGroup> </Fragment> <Fragment> <!-- vcredist 2013

问题 This question is asking whether one of the ICE57 validators creates a false positive error report. I am using WIX 3.9 to generate an installer. I want a per machine installation with non advertised shortcuts. This WXS example installs a text file and a shortcut to open the text file: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Product Id="*" Name="ShortcutTest" Language="1033" Version="1.0.0.0" Manufacturer="Widget Co" UpgradeCode="--YOUR

问题 I'm creating an installer for my application using WIX. Everything works fine so far. However, I'm trying to create a new event source during installation and that doesn't work as expected. I've read and understood this question here on SO, but I have a somewhat different situation in which the given solution does not seem to work properly. The following is done differently: I'm using the WixNetFxExtension to determine whether .NET 3.5 is installed as a startup condition. I'm using the

问题 Edit: I've updated the code below so that it now works, thanks to Rob's answer. I've found a couple of pages that show how to do this (http://www.cmcrossroads.com/content/view/13160/120/, http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg05103.html) and looked through the source code for WAI (http://wai.codeplex.com/), but I can't seem to get it to work in my installer no matter what I try. If anyone can spot what I'm doing wrong I'd be very grateful. My WiX fragment for the