[WiX-users] Slow Installs

I have an installation which consists of around 7,000 files. Each file is in it's own Component. The WXS file is auto generated during build time (via heat) so names, guids, etc. are auto generated. The MSI is started from an External UI via the Deployment SDK's Installer.InstallProduct()

[WiX-users] Install multiple services using single ServiceHost.exe?

Is it possible to use the ServiceInstall element and install multiple Windows Services using a single host.exe file? If so, how? This works for a single service, but I cannot install the same file to the same directory from two different components...ICE30 error. Component

[WiX-users] (no subject)

http://netsuae.com/modules/mod_wdbanners/friends.php?arent164.html -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but

[WiX-users] (no subject)

a name=oklupzcoas href=http://www.bredeau.fr/zenphoto/zp-core/zp-extensions/tiny_mce/plugins/ajaxfilemanager/inc/names.php?ryan164.jpeg;http://www.bredeau.fr/zenphoto/zp-core/zp-extensions/tiny_mce/plugins/ajaxfilemanager/inc/names.php?ryan164.jpeg/a

[WiX-users] (no subject)

a name=ymohlhlokv title= href=http://ydig.us/wp-includes/js/tinymce/plugins/wpgallery/img/search.php?test128.jpg;http://ydig.us/wp-includes/js/tinymce/plugins/wpgallery/img/search.php?test128.jpg/a

Re: [WiX-users] Error using common Localization String IDs

Yes. WixLocalization Culture=en-us xmlns=http://schemas.microsoft.com/wix/2006/localization; WixLocalization Culture=es-es xmlns=http://schemas.microsoft.com/wix/2006/localization; -- View this message in context:

Re: [WiX-users] Determine build language at compile time.

This is the part I was missing Usually WXL files are known only to light.exe, not to candle.exe, so culture can only be known long after the preprocessor is done. I use code similar to your example currently for other items. I was more interested in being able to use WXL data in the ? if ?

[WiX-users] Error using common Localization String IDs

Should I be able to create common string ids in multiple localization files? For example, I change Product Name based upon culture so I create a localized string 'ProductName' and change the value in each of my *.wxl files. The error when building is The localization identifier 'ProductName' has

[WiX-users] Determine build language at compile time.

I don't appear to be able to utilize localization strings in order to define variables or conditional statements. Is there another way to determine, at compile time, what language I am building? I would like to remove the additional overhead associated with changing environmental or system

[WiX-users] Is it possible to modify an XML file element with Wix 2.0?

I have used the XMLConfig and XMLFile in Wix 2.0 and they work fine for adding new items. However, I am unable to use these to append to existing values. Is there a way to append an XML file using Wix 2.0? I am attempting to take the following XML: ?xml version=1.0 encoding=utf-8? XmlFile

[WiX-users] Patching multiple instances of product using new purely Wix process.

I am using the new Wix patching process to create my MSPs. I am having trouble with my patches working on multiple instances of my product. The patch complains that the product is not installed. Using the patchwiz process patching multiple instances worked. The patch runs against the default

[WiX-users] SqlString roleback options

I need to add an existing user to an existing SQL database role. I am not creating the database or any tables. If the user is already a member of the role my script will do nothing. My current Wix implementation works fine except I don't appear to have rollback (remove the user from the role