You can use a Directory Id like a property.
E.g. You can have
<Directory Id="TARGETDIR" Name="SourceDir">
<Directory Id="ProgramFilesFolder" Name="PFiles">
<Directory Id="PRODUCTDIR" Name="MyProduct">
... Components ...
</Directory>
</Directory>
</Directory>
You can then use a Custom Action (or I guess the RegSearch action directly) to
set PRODUCTDIR like
you would a normal property. All the child directories below it will also get
resolved as expected.
Rob
Koloszar Jozsef wrote:
> hi,
> i'm trying to write an installer for an addon. the dumb way, but i have to.
>
> i'm reading the main install path of the main/parent app from registry. it
> is stored there as a full path string like "D:\Not Program
> Files\InstalledHereInstead\Foo App\"
>
> i read it using
> <Property Id="INSTALLDIR">
> <RegistrySearch Id='mainprogdirsearch' Type='raw'
> Root='HKLM' Key='Software\Foo App\Setup Info' Name='locprogdir' />
> </Property>
> and i'm guessing it gets read because a condition on INSTALLDIR is not
> triggered.
>
> but here's my problem:
> how do i then use this nice string path to actually specify the install
> location, that is otherwise and normally done by neatly nesting
> <Directory>-s one depth at the time
>
> thanks for your time end efforts in advance.
> jozsef koloszar,
> hungary
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
