Balakrishna.BK wrote:
> Thanks Bob,
>I am using a Generic wix template in my company..so I am not aware
> of this.
> The template had sequence numbers, for LaunchCondition it was 100 and
> then for Appsearch 400.
WiX automatically sequences standard actions so there's almost no reason
to gi
John Lalande wrote:
> Since no other product will use this component, this is exactly what I
> want. Is there any other gotchas you know of that I should be aware of?
No, that's the odd behavior that makes it unsuitable for some cases. If
it doesn't apply, you should be good to go.
--
sig://b
Setting the Transitive attribute to 'yes' gives me a merge module that does
exactly what I need.
Nonetheless, you advised me to read the SDK docs for this attribute and I
found the following:
"If this bit is set, the installer reevaluates the value of the statement in
the Condition column upon a
John Lalande wrote:
> I would like to further enhance this merge module such that if a user
> later installs Act, then they run a Repair, it will install this
> component. I suspect that this isn't possible as a Repair is simply
> repairing the components that are already installed.
>
> Or is t
Updating the merge module code as you explained works perfectly. Thanks for
that!
I would like to further enhance this merge module such that if a user later
installs Act, then they run a Repair, it will install this component. I
suspect that this isn't possible as a Repair is simply repairing
Balakrishna.BK wrote:
>
That's the default sequencing in WiX and has been for many months.
Unless you're using a very old build of WiX, that shouldn't be necessary.
--
sig://boB
http://bobs.org
-
Take Surveys. Earn Cash
John Lalande wrote:
>
>
>
> Guid='31A99920-6E0A-4e31-B569-180D46439930'>
> src='NHPlugin.dll' />
> ACTPATH <> ""
>
>
>
>
>
> What happens when Act! is not installed is that the plugin is
> installed in c:\ActD
code from my wxs file
SUITEINSTALLDIR
Thanks,
Bala.
Message: 3
Date: Wed, 28 Feb 2007 14:21:41 -0600
From: "John Lalande"
Subject: [WiX-users] merge module that conditionally installs a
component
To:
I have created a plugin for the PIM Act! This plugin dll must be installed
in a subfolder of the Act! installation directory only if Act! is installed.
I would like to package the plugin in a merge module so that different teams
at our company can use it by simply including it in their installer
9 matches
Mail list logo
