![\"VS2012_ToolsOptionsDirectories\"](\"http:\/\/www.curlybrace.com\/words\/wp-content\/uploads\/2012\/12\/VS2012_ToolsOptionsDirectories.png\")
<\/p>\nStarting with Visual Studio 2010, Microsoft decided to make life hard on C++ developers. \u00a0System-wide include path settings used to be accessed through Tools | Options | Projects and Solutions | VC++ Directories. \u00a0However, that option is gone:<\/p>\n
<\/p>\n
Instead, the system-wide include paths are now located within the ‘Properties’ interface. \u00a0To access it, select View | Property Manager. \u00a0No dialog will appear yet. Instead, the Property Manager appears as a tab along with the Solution Explorer:<\/p>\n
![\"VS2012_OptionsPropertyManager\"](\"http:\/\/www.curlybrace.com\/words\/wp-content\/uploads\/2012\/12\/VS2012_OptionsPropertyManager.png\")
<\/p>\n
\n Note: \u00a0The Property Manager won’t contain anything unless a solution is loaded.<\/strong>\n<\/p>\n If the Property Manager is missing, it can be shown by selecting View | Other Windows | Property Manager from the menu.<\/p>\n Now, expand one of your projects, then expand Debug | Win32 or Release | Win32:<\/p>\n Right click Microsoft.Cpp.Win32.user and select Properties: This brings up the Microsoft.Cpp.Win32.User Property Pages dialog, which should look familiar enough:<\/p>\n %LOCALAPPDATA%\\Microsoft\\MSBuild\\v4.0\\Microsoft.Cpp.Win32.user.props<\/tt><\/p>\n Starting with Visual Studio 2010, Microsoft decided to make life hard on C++ developers. \u00a0System-wide include path settings used to be accessed through Tools | Options | Projects and Solutions | VC++ Directories. \u00a0However, that option is gone: Instead, the … Continue reading ![\"VS2012_PropertyPageProjectExpanded\"](\"http:\/\/www.curlybrace.com\/words\/wp-content\/uploads\/2012\/12\/VS2012_PropertyPageProjectExpanded.png\")
<\/p>\n![\"VS2012_PropertyPageProjectExpandedMenu\"](\"http:\/\/www.curlybrace.com\/words\/wp-content\/uploads\/2012\/12\/VS2012_PropertyPageProjectExpandedMenu.png\")
<\/p>\n![\"VS2012_Win32UserPropertyPage\"](\"http:\/\/www.curlybrace.com\/words\/wp-content\/uploads\/2012\/12\/VS2012_Win32UserPropertyPage.png\")
<\/p>\nAlternate Access The properties can be accessed directly as an XML file by editing<\/h3>\n
![\"VS2012_Win32UserPropsXML\"](\"http:\/\/www.curlybrace.com\/words\/wp-content\/uploads\/2012\/12\/VS2012_Win32UserPropsXML.png\")
<\/p>\nRant: None of this makes any sense whatsoever. Why do I have to have a solution loaded before I can edit the system-wide (technically user-wide) path settings? \u00a0The old system made sense: project-specific include paths were set in the properties of individual projects, and system include paths were set through the Tools menu. The layout is irritating, forgettable, and, most importantly, it makes absolutely no sense to access system settings by clicking through your own projects!<\/h3>\n","protected":false},"excerpt":{"rendered":"