wix3

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="raw"> <DirectorySearch Id="SPIniFilePath" Path="[CFGPATH]"> <FileSearch Id="SPIniFile" Name="sp.ini"/> <

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 command line (hard coded at the moment) it works fine. However, when run during an install, it fails.

I need to display the version number in the title along with the application name. Currently, it looks like Here is my wix snippet: <Product Id="$(var.ProductId)" Name="Test Application" Language="1033" Version="$(var.ProductVersion)" Manufacturer="Test1111 Inc" UpgradeCode="C9BC6B42-FCAF-4E96-8F8F-E9D0AC4F393B"> If I change it (append version number in the Name attribute) as below, it will display the version number in all the places Title, Welcome text/description but I just want to change in Title. <Product Id="$(var.ProductId)" Name="Test Application $(var.ProductVersion)" Language="1033"

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 dialogue looks like this: <UI> <Dialog> ...snip... <Control Id="WebsiteName" Type="ComboBox" ComboList

I am facing issues when migrating the managed code from x86 to x64 platform. I have a WiX project to create an MSI which will be executed through Bootstrapper. On an x86 platform, files get copied in “Program Files” as per the Project.wxs file. But if the same MSI is installed on an x64 platform through Bootstrapper, all the installation files get copied by default in “Program Files (x86)” and the application’s functionality failed as it could not find the necessary files in the 12-hive hierarchy of Program Files (for 64-bit it is “C:\Program Files\Common Files\Microsoft Shared\web server

I am learning Wix and I want to generate a setup.exe file instead of a setup.msi. Is that possible? A setup EXE is usually referred to as a bootstrapper or chainer . WiX 3.5 will ship with an executable called burn.exe , unfortunately this is still under heavy development. If you're just after a basic self-extracting EXE with no additional logic you can use the included setupbld.exe with WiX. However it's pretty limited and only includes the most basic functionality. Alternatively, 7-zip includes basic functionality for creating a setup.exe from an existing MSI. You will need to install the

I am fairly new to WIX, so forgive me if I'm completly missing the boat here, but I was wondering if it was possible to reuse components (mwm,cab,etc) from within a wxs file without having light re-link them every time. The installer I'm working on has several executables, dlls and config files that tend to change between each install. These files amount to about 5 meg worth of installer. The part I want to reuse is the ~350 meg worth of image/map/database files that do not change very often that I don't want to necessarilly have to compile/link every time the installer is built. I've tried

Good day. I've been building an installer for our product using the WIX(Windows Installer XML) technology. The expected behavior is that the product is launched, if the check box is checked after installation. This has been working for some time now, but we found out recently that UAC of Win 7, and Vista is stopping the application from launching. I've done some research and it has been suggested to me that I should add the attributes Execute='deferred' and Impersonate='no'. Which I did, but then found out that to execute deferred, the CustomAction has to be performed, between the