Bugs item #1096614, was opened at 2005-01-05 12:14 Message generated for change (Comment added) made by rblum You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1096614&group_id=31650
Category: Tasks Group: 0.85 Status: Open Resolution: None Priority: 5 Submitted By: Bill Arnette (billarnette) Assigned to: Nobody/Anonymous (nobody) Summary: solution task: C++ and includevsfolders Initial Comment: Ever wonder where all those paths you specify in the VS.NET IDE Tools->Options->Projects->VC++ Directories dialog are stored? Well, they are stored in a file called VCComponents.dat in the folder C:\Documents and Settings\<username>\Local Settings\Application Data\Microsoft\VisualStudio\7.1. This file is a INI format file where the 'key' part of the key/value pair is a path type and the 'value' is a semicolon delimited list of paths. The paths can have macros such as $(VSInstallDir). It appears that before invoking a tool, such as cl.exe, the IDE adds these paths (after resolving the macros of course) to the INCLUDE, LIB, and PATH environment variables. The following table summarizes the mapping of keys to environment variables. Path Type Environement Var ----------- ----------------- Path Dirs PATH Include Dirs INCLUDE Library Dirs LIB Reference Dirs LIBPATH(?) Source Dirs ??? IMHO, the 'includevsfolders' attribute of the solution task should do as the IDE does, and append these paths to the environment before invoking a tool. The $(VSInstallDir) and $(VCInstallDir) macros can be resolved from the registry. ---------------------------------------------------------------------- Comment By: Robert Blum (rblum) Date: 2005-04-27 01:00 Message: Logged In: YES user_id=25786 Can I add a vote for this bug? Also, to be semi-useful here: The data is stored in the INI section with the name "[VC\VC_OBJECTS_PLATFORM_INFO\Win32\Directories]" Replace Win32 with the appropriate platform. (Does nant support other platforms? I never tried....) ---------------------------------------------------------------------- Comment By: Philip Craig (philipcraig) Date: 2005-02-07 04:13 Message: Logged In: YES user_id=68755 I agree on both points (finding the stuff from the registry, and settings incudevsfolders.) In this way NAnt's solution task would more closely resemble what invoking devenv.exe from the command line does. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1096614&group_id=31650 ------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ nant-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nant-developers
