You're stretching what can be done with a Visual Studio setup project. I
wouldn't bother to search for the folder, I'd just install the file at:
[CommonFilesFolder]Microsoft Shared\VS Help
Data\8.0\Filters\[UserLanguageID]
Those property names are case-sensitive. [CommonFilesFolder] gets you to the
common files folder, and UserLanguageID will be 1033 or 1041 depending on
the users language spec on the system. Install the english file if
UserLanguageID=1033, otherwise the Japanese one.

Signature
Phil Wilson [MVP Windows Installer]
----
Hi Phil,
In this case, it will create the directoy if it doesn't exist.
How in the setup program to specify that copy the file only if the folder
exists?.
Also I have to create a registry key in hive-
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Help\VisibleFilters
(if this hive already exists). How to do this, because this should not
create the hive if it doesn't exist.
Also, how to know which version of VS is installed?(2003/2005).
Thanks for your help.
Sajith
> You're stretching what can be done with a Visual Studio setup project. I
> wouldn't bother to search for the folder, I'd just install the file at:
[quoted text clipped - 48 lines]
> >> > Thanks,
> >> > Sajith
Phil Wilson - 20 Feb 2006 20:46 GMT
Yes it will create the directory, but is that such a bad thing? The issue is
that you can't do what you want to do with a Visual Studio setup project
because there's no IDE support for adding code to look for folders or
registry keys before the install. The least pain alternative is just to
install it as I described and create the directory. There are about 20 other
tools that can generate MSI setups, and Visual Studio just doesn't let you
do the things that tools from InstallShield, Wise etc can do.
I can't think of a good way to detect VS 2003 or 2005 for you. There might
be registry entries. I'd normally use the MSI APIs to see if their product
Guids are installed, such as:
{437AB8E0-FB69-4222-B280-A64F3DE22591} Microsoft Visual Studio 2005
Professional Edition - ENU
{E05F0409-0E9A-48A1-AC04-E35E3033604A} Visual Studio .NET Enterprise
Architect 2003 - English
and then launch the MSI file with a command line indicating which are there
(both of them could be there).

Signature
Phil Wilson
[Microsoft MVP-Windows Installer]
> Hi Phil,
>
[quoted text clipped - 68 lines]
>> >> > Thanks,
>> >> > Sajith
sajithpt - 23 Feb 2006 06:24 GMT
Hi Phil,
Thanks a lot for your help.
Sajith
> Yes it will create the directory, but is that such a bad thing? The issue is
> that you can't do what you want to do with a Visual Studio setup project
[quoted text clipped - 87 lines]
> >> >> > Thanks,
> >> >> > Sajith