Wanto to set my installation to FS2002DIR\Scenery\Myfolder
Note: a CA is defined for TARGETDIR
TNX to ALL who HELP ME.
I then run my custom action to find the registry value I want. I then use a
Windows Installer API call to set the NEWDIR property to the value I have
found.
I have placed this action after MigrateFeatureStates.
This is probably not the easiest way to do this, maybe someone else knows
how to do it by just using the windows installer engine and no custom
action?
cheers
"David" <cut...@tin.it> wrote in message
news:130e101c222ec$a973ccc0$a4e62ecf@tkmsftngxa06...
After i've set that to 1 it works properly, you don't
need to make external call, in the AppsSearch only
specify TARGETDIR as Property, and all works!!!
APPS_TEST: This property provides backwards compatibility for the System
Search page for installations created in Wise for Windows Installer 2.0.
It sounds like you're working with an install created by an old version of
WfWI.
"David" <cut...@tin.it> spake the secret code
<130e101c222ec$a973ccc0$a4e62ecf@tkmsftngxa06> thusly:
>The TARGETDIR is fixed, how to read
>from registry the path to set the TARGETDIR of my package?
>What i need to do exactly step by step to do this?
>I've tried to manage Reglocator and other things but i'm
>newbie, pls HELP me
>This is what i want to do:
>Path to find: Microsoft Flight Simulator 2002
>registry path of stored path:SOFTWARE\Microsoft\Microsoft
>Games\Flight Simulator\8.0
>key: EXE Path
>
>Wanto to set my installation to FS2002DIR\Scenery\Myfolder
What I would do is use AppSearch to locate that directory and set the
TARGETDIR property to the directory name. Everything else will follow
as normal. I've done this with a simple install that added a visual
studio macro file to the appropriate directory on a machine with
visual studio installed. So I know it can be done.
To debug the AppSearch action, I like to display the property set by
the action in the first dialog that appears. Then I can check right
away that I have the proper AppSearch recipe before the installation
goes any farther. I just modify the text of one of the controls on
the Welcome dialog to contain the property set by AppSearch.
--
Ask me about my upcoming book on Direct3D from Addison-Wesley!
Direct3D Book <http://www.xmission.com/~legalize/book/>
izfree: Open source tools for Windows Installer
<http://izfree.sourceforge.net>
"David" <cut...@tin.it> spake the secret code
<132c701c22353$4b13ed10$a4e62ecf@tkmsftngxa06> thusly:
>Ok, i managed that after several days of working with
>AppsSearch function, the sdk documentation is very poor
>in my opinion it not mention to set APPS_TEST 1 in
>property page.... :((
That's because APPS_TEST is not part of Windows Installer, its coming
from whatever you used to author your MSI. Remember that the MSI
database is arbitrarily extensible, so just because you find it in
your MSI generated by authoring tool XYZ doesn't mean that you will
find documentation on it in the core SDK documentation. If you don't
find it in the core SDK docs, then you should check the docs/support
website of the vendor for your tool.