I have recently upgraded from VC6 to NET2003. So I am a bit unfamiliar
with much of the new terminology and organization.
My NET2003 project was building successfully yesterday afternoon.
I made some configuration tweaks, adding path definitions to Tools -
Options - Projects area.
Suddenly, all of my NET2003 projects are failing to build on that particular
development box.
I restored my project files from configuration store, but this did not
correct the problem.
So NET2003 must be saving some config data in some platform, global store
(registry?)
I am getting: "command line error MIDL1005 - cannot find C preprocessor
cl.exe"
I EVEN did a full uninstall and reinstall of NET2003 to no avail.
These same project files do compile on my second development box BTW, so the
project files
should be sound.
I compared the Tool - Options - Projects - configuration settings and the
two boxes appear to agree.
Where are the NET2003 global settings stored, and how does one access/manage
them?
Thanks,
Paul
Paul Bouche - 20 Feb 2004 22:23 GMT
Issue solved...
I must have accidentally modified a Tool-Option-Project
-VC++Directory path for executables
from: $(VCInstallDir)bin
to: $(VSInstallDir)bin
Likely everyone in this group already knows this, but...
it seems this configuration data is save in a file called
VCComponents.dat under the path....
c:\Documents and
Settings\usernamexxx\LocalSettings\ApplicationData\Microsoft\VisualStudio\7.
1 folder.
Since my uninstall and reinstall of NET2003 Studio did not fix this
problem, I presume this hidden storage area was not deleted by the
uninstall. Hence upon re-install, it was still there to trip me up.
Alas.
Thanks for any who may have spent time reading this.
Paul