Visual Studio 2010

I actually like using Visual C++, and have for some time.  While I also like Code::Blocks, VC++ is the easiest way to get going for Windows development.  And since they started releasing the Express editions, cost isn't much of an issue.

I recently installed VC++ 2010 Express, and while there are a number of nice things about it (Intellisense seems better, for example,) there is an issue that really frustrates me.  As someone who develops in an environment where I constantly use proprietary libraries, I need the IDE to know where these libraries are located.  Previous versions allowed you to add these directories via the Tools->Options->Projects and Settings->VC++ Directories setting.  This has now been deprecated, favoring per-project directories.  It is still possible to adjust the global directories, though I don't believe it is as straight-forward as it should be.  In order to set directories to be used for ALL projects, you must first have a project open in the IDE.  Next, select View->Property Manager from the menu (you may need to select Tools->Settings->Expert Settings to have this option visible).  From here, expand one of the configurations and right-click the Microsoft.cpp.<platform>.user property page and select Properties.

You will now be able to select VC++ Directories and edit the global directories, just as you had in previous versions.

Note that you only need to do this in one configuration (ie. Debug or Release in the above example) and it will be applied to all.

While this does, in fact, work and isn't terribly difficult (once you figure out where to find it), I am still upset that the Visual Studio team thought this was a good idea.  First let's try to examine their logic for this illogical move: to prevent casual users from putting every library directory into every project.  There are reasons why this can be considered a good idea, but if the change was made to benefit more advanced users, then why?  It was ALREADY POSSIBLE via the project settings, using the Additional Includes and Additional Libraries settings.  These settings were, and still are, per-configuration, but the point is, advanced developers would only set the global directories to those that would be used all the time, then adjust the project directories to those needed for the given project.  In nearly any professional environment, the development team will have some custom libraries that they include in most all projects.  I have custom graphics and math libraries that I include in all of my projects, save for some simple test programs I write on occasion.

My feeling is that by changing the location of the global directories, the Visual Studio team is frustrating many of the professional developers and alienating the hobbyists.  Bad move, Microsoft.