Discussion:
Where is $(VCInstallDir) defined ?
(too old to reply)
Polaris
2006-12-20 22:59:33 UTC
Permalink
Hi Experts:

In Visual Studio, under Tools - Options - Projects - VC++ Directories, I see
many environmental variables like: $(VCInstallDir), $(FrameworkSDKDir)...
Where are those defined?

Thanks in Advance!
Polaris
Igor Tandetnik
2006-12-20 23:42:18 UTC
Permalink
Post by Polaris
In Visual Studio, under Tools - Options - Projects - VC++
$(VCInstallDir), $(FrameworkSDKDir)... Where are those defined?
IDE automatically defines them at startup. Values for these two most
likely come from registry.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
Alex Blekhman
2006-12-21 08:27:55 UTC
Permalink
Post by Polaris
In Visual Studio, under Tools - Options - Projects - VC++
$(VCInstallDir), $(FrameworkSDKDir)... Where are those
defined?
In addition to Igor's reply, you can see most of these
variables by executing "SET" command (without parameters) at
Visual Studio command prompt.

Alex
Polaris
2006-12-21 18:05:31 UTC
Permalink
Thanks guys.

Kind of strange, they are not in registry, and not in the output of "set"
either...
Post by Polaris
In Visual Studio, under Tools - Options - Projects - VC++ Directories, I
see many environmental variables like: $(VCInstallDir),
$(FrameworkSDKDir)... Where are those defined?
In addition to Igor's reply, you can see most of these variables by
executing "SET" command (without parameters) at Visual Studio command
prompt.
Alex
Igor Tandetnik
2006-12-21 18:27:56 UTC
Permalink
Post by Polaris
Post by Polaris
In Visual Studio, under Tools - Options - Projects - VC++
$(VCInstallDir), $(FrameworkSDKDir)... Where are those defined?
In addition to Igor's reply, you can see most of these variables by
executing "SET" command (without parameters) at Visual Studio command
prompt.
Kind of strange, they are not in registry
I have "ProductDir" value under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1\Setup\VC

registry key: that's likely where the value of $(VCInstallDir) comes
from. Similarly, the value for $(FrameworkSDKDir) probably comes from

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework
sdkInstallRootv1.1
Post by Polaris
and not in the output of "set" either...
Go to View | Other Windows | Command window. Once in the command window,
type the following line

Tools.Shell /c cmd /c set

This executes "set" command from inside Visual Stuio, so you see the
same environment variables the IDE sees.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
Polaris
2006-12-21 18:30:07 UTC
Permalink
Yes, they are shown in the output of "set" under the VS .Net Tool - VS
Command Prompt (Installation group menus). So they are dynamically
set/defined.

Thanks
Polaris
Post by Polaris
Thanks guys.
Kind of strange, they are not in registry, and not in the output of "set"
either...
Post by Polaris
In Visual Studio, under Tools - Options - Projects - VC++ Directories, I
see many environmental variables like: $(VCInstallDir),
$(FrameworkSDKDir)... Where are those defined?
In addition to Igor's reply, you can see most of these variables by
executing "SET" command (without parameters) at Visual Studio command
prompt.
Alex
Schemer
2006-12-24 15:56:09 UTC
Permalink
In your <VisualStudioInstallDir>\Common7\Tools dir you will find
vsvars32.bat.

It will set up a command shell's environment, much like using the
"Start->All Programs->Microsoft Visual Studio 2005->Visual Studio
Tools->Visual Studio 2005 Command Prompt".
Post by Polaris
In Visual Studio, under Tools - Options - Projects - VC++ Directories, I
see many environmental variables like: $(VCInstallDir),
$(FrameworkSDKDir)... Where are those defined?
Thanks in Advance!
Polaris
Loading...