"Rob Lambert" <rlambert@schange.com> wrote in message
news:ov44uvonluu2ilbh9hngea0e5bj2he98po@4ax.com...
> Hi,
> Whats the "recommended" way to check to see if a path is already on in
> the PATH environment variable, and if not, to put it there during the
> installation.
>
> And... how do you detect it and remove it if detected during uninstall
> operations?
>
> I can do a registry search to get the current value of the PATH
> I can structure the registry entry to add my install path to the PATH
>
> but I can't figure out how to test the pre-installation PATH value for
> the presence of the application specific path that I need to install
> (for instances of upgrade installations).

"Rob Lambert" <rlambert@schange.com> wrote in message
news:mjm6uvkeot8he91t5fthlenvt10tik78jk@4ax.com...
> On Fri, 19 Dec 2003 11:24:15 -0800, "Phil Wilson"
> <phil.wilson@unisys.spamcom> wrote:
>
> >The general answer in the Windows Installer world is to use the Environment
> >Table (see Platform SDK, Windows Installer section). VS setup projects don't
> >give you an IDE interface to this however, so you'd need to edit the MSI file
> >manually with Orca to add your entry. There's a "create if it doesn't exist"
> >choice.
>
> I saw a reference to Orca in another threa on this topic, but I have
> no idea what it is, neither does anyone I work with, and I can't find
> any other references to it in these newsgroups.
>
> what is Orca?

<phil.wilson@unisys.spamcom> wrote:

>The general answer in the Windows Installer world is to use the Environment
>Table (see Platform SDK, Windows Installer section). VS setup projects don't
>give you an IDE interface to this however, so you'd need to edit the MSI file
>manually with Orca to add your entry. There's a "create if it doesn't exist"
>choice.