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.
--
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 there
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:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='ACTPATH' Name='ActDir'
Directory Id='PluginsDir' Name='Plugins'
Component Id='Plugin'
Guid='31A99920-6E0A-4e31-B569-180D46439930'
File Id='NHPlugindll' Name='NHPlugin.dll'
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
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
2007 14:21:41 -0600
From: John Lalande
Subject: [WiX-users] merge module that conditionally installs a
component
To: wix-users@lists.sourceforge.net
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1
I have created a plugin for the PIM Act! This plugin dll must
7 matches
Mail list logo
