Re: [WiX-users] Detection of run-time DLLs

Thanks for reply to all who answered. I would try to summarize. 1. The features of dependency detection (as seen in InstallShiled and Package and Deployment projects) are not part of the WiX toolkit. There is no way to generate any .wxs source that can be used in the installer neither with WiX

[WiX-users] How to use a particular version of runtime merge modules?

All of our software – both 3rd-party and in-house – is built against a particular version of the VS/VC runtimes – specifically "9.0.30729.4148". How does one utilize merge modules in Wix sources using a particular manifest/version of the VS/VC runtimes? Thanks, Eric. -

Re: [WiX-users] Help with updating Heat output files to be installed into GAC

Thank you very much. It worked like a charm! On Tue, May 17, 2011 at 6:31 PM, jhennessey wrote: > I'm using the heat task for MSBuild so I just specify the path to my xlst > file with the Transforms property. Here's an abbreviated example: > > > > You can also specify it with the -t parameter on

Re: [WiX-users] Help with updating Heat output files to be installed into GAC

I'm using the heat task for MSBuild so I just specify the path to my xlst file with the Transforms property. Here's an abbreviated example: You can also specify it with the -t parameter on the commandline. Look at the WiX chm file for more details. -- View this message in context: http://windo

Re: [WiX-users] Help with updating Heat output files to be installed into GAC

Thanks, how are you calling this from your Wix project? On Tue, May 17, 2011 at 4:27 PM, jhennessey wrote: > You can specify an XSL transform to apply after heat harvests the files. > Here's what my xslt file looks like: > > > > xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; >xmlns:msxs

Re: [WiX-users] Help with updating Heat output files to be installed into GAC

You can specify an XSL transform to apply after heat harvests the files. Here's what my xslt file looks like: http://www.w3.org/1999/XSL/Transform"; xmlns:msxsl="urn:schemas-microsoft-com:xslt" exclude-result-prefixes="msxsl" xmlns:Wix="http://schemas.microsoft.com/wix/2006/wi";>

Re: [WiX-users] Creating patch / AssemblyFileVersion

Windows Installer (and by extension, tools that use/depend on it, such as MsiMsp.exe/PatchWiz.dll & the WiX toolset) use the published versioning rules published on MSDN. Those state that when FileVersion (aka AssemblyFileVersion for those building managed modules/assemblies) exists in a binary the

Re: [WiX-users] How to cache msi for Modify/Repair to use

Hi Mat, Thanks a lot for the very useful information. If you can, please also share with us your merge module code. Thank you, Miaohsi -Original Message- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Tuesday, May 17, 2011 8:58 AM To: General discussion for Windows Inst

Re: [WiX-users] How to cache msi for Modify/Repair to use

Do you have a ResolveSource action in your Sequence tables ? If so, search on this list for "resolveSource" for some ideas about how to handle it. -Original Message- From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com] Sent: 17 May 2011 16:44 To: General discussion for Windows Installer

Re: [WiX-users] How to cache msi for Modify/Repair to use

There is no generic way to do this, You will basically have to write your own custom actions that does this task and updates the source list for the MSI package. I personally created a merge module with a set of actions that cache the MSI in a set location and handle any cleanup and registratio

Re: [WiX-users] Help with updating Heat output files to be installed into GAC

Is anyone aware of a way to add assembly=".net" to files that need to be installed in the GAC during the harvesting of files using Heat? On Mon, May 16, 2011 at 1:33 PM, CoolBreeze wrote: > Hi, > > I'm trying during the harvesting of files with Heat to update the resulting > *.wxs file adding ass

[WiX-users] How to cache msi for Modify/Repair to use

Dear All, After installing our product, doing Modify/Repair from the "Add Remove Programs" window requires the original install package to be in the same location where the product is installed from. Does anyone know how to cache msi locally such that Modify/Repair the product via "Add Remove P

[WiX-users] (no subject)

-- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlc

Re: [WiX-users] Failure Injection for Upgrade/Rollback Testing

This may be useful too http://wix.sourceforge.net/manual-wix3/wixfailwhendeferred.htm -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: 17 May 2011 00:44 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Failure Injection for U

Re: [WiX-users] Conditionnal Installation of Component

Comments inline. Rob On 16/05/2011 18:22, Sylou wrote: > Hello everyone, > > I'm new to WIX. Yes another > > > > OK, I have a Modular Client-Server Application to > Install. > > I could have 3 type of installation: > > 1- Client > > 2- Server > > 3- Client and Server on the same co