Bugs item #1096614, was opened at 2005-01-05 18:14 Message generated for change (Comment added) made by bestlem You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1096614&group_id=31650
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. 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: Mark Bestley (bestlem) Date: 2005-07-21 23:46 Message: Logged In: YES user_id=208501 I definitely would not want this to happen by default. The reason is that is 2 developers have different IDE settings then the nant build will give different results. However the current behaviour is the same as devenv /usenv and the requested behaviour is devenv without the /useenv flag. (I always use the former) ---------------------------------------------------------------------- Comment By: Robert Blum (rblum) Date: 2005-04-27 07: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 10: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: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
