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 the
components that are already installed.

Or is there a way around this?

John

On 3/1/07, Bob Arnson <[EMAIL PROTECTED]> wrote:

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'
> src=' NHPlugin.dll' />
>                 <Condition>ACTPATH &lt;&gt; ""</Condition>
>             </Component>
>         </Directory>
>     </Directory>
> </Directory>
>
> What happens when Act! is not installed is that the plugin is
> installed in c:\ActDir\plugins which does make sense because in the
> absence of the ACTPATH property, "ActDir" is set as the actual name of
> the folder.  So it is clear that I don't have a good understanding how
> this should be written.

I think the problem is that the directory ACTPATH has a value regardless
of whether the RegistrySearch found something. The easiest way is
probably to have a duplicate RegistrySearch and use that property in the
component condition.

--
sig://boB
http://bobs.org



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to