: [WiX-users] one MSI Installer for all Environments as single a
package
Hi Jacob,
I think using XSLT we can skip unwanted elements while running HEAT.EXE command
in that case we will need to build project for each of the Environment by
giving XSLT Template as parameter to Heat.exe. If I am
Hi Jacob,
I think using XSLT we can skip unwanted elements while running HEAT.EXE
command in that case we will need to build project for each of the
Environment by giving XSLT Template as parameter to Heat.exe. If I am wrong
please correct me. In that case we will need to create four MSI one for e
M
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] one MSI Installer for all Environments as single a
package
Hi Jacob,
Thanks for the reply..
I need to have single Instance MSI as a package.And based on your reply ,Seams
like it should be property driven. And Can you point out me so
Hi Jacob,
Thanks for the reply..
I need to have single Instance MSI as a package.And based on your reply
,Seams like it should be property driven. And Can you point out me some
"remember me pattern and conditions on the components" and how some
components can be filtered(skipped) from harvest.wx
Do you need to support multiple instances on the same box?
If yes, you need to look at instance transforms. If no, then property drive the
install using the remember me pattern and conditions on the components for each
instance. If the differences are all config based, you could use ca's to writ
Hi we have requirement such that need to create a single MSI package of a web
application for all the Environments(UAT,DEV,TEST,PROD) such that we pass
parameter(Environment) to MSI Installer during installation;based on that we
need to get those Environment files(config files) installed and filter
6 matches
Mail list logo