Comments on: Visual Studio 2012 First Impressions https://codesynthesis.com/~boris/blog//2012/10/09/visual-studio-2012-first-impressions/ Boris Kolpackov's blog about software Tue, 14 Apr 2026 09:10:17 +0000 http://wordpress.org/?v=2.2.2 By: Boris Kolpackov https://codesynthesis.com/~boris/blog//2012/10/09/visual-studio-2012-first-impressions/#comment-2352 Boris Kolpackov Thu, 11 Oct 2012 12:44:50 +0000 https://codesynthesis.com/~boris/blog//2012/10/09/visual-studio-2012-first-impressions/#comment-2352 Kenneth, the problem with this approach is it requires modification of each project. In my case that would be hundreds of them. Plus, what I am looking for here is the equivalent to /usr/{include, lib} on UNIX; i.e., a mechanism to locate common headers/libraries (e.g., database access libraries) without having to hardcode non-portable locations into project files/makefiles. Kenneth, the problem with this approach is it requires modification of each project. In my case that would be hundreds of them. Plus, what I am looking for here is the equivalent to /usr/{include, lib} on UNIX; i.e., a mechanism to locate common headers/libraries (e.g., database access libraries) without having to hardcode non-portable locations into project files/makefiles.

]]> By: Kenneth Benzie https://codesynthesis.com/~boris/blog//2012/10/09/visual-studio-2012-first-impressions/#comment-2351 Kenneth Benzie Wed, 10 Oct 2012 19:36:13 +0000 https://codesynthesis.com/~boris/blog//2012/10/09/visual-studio-2012-first-impressions/#comment-2351 Your issue pertaining to your include and library directories and so forth. Have you looked into creating your own Property Sheets instead of editing Microsoft.Cpp.Win32.User or Microsoft.Cpp.x64.User directly? This way you can set specific properties per solution/project and keep things separate if so required. Alternatively properties that are not specific to a solution can be shared by loading the same Property Sheet in the various projects where required. I suspect this would avoid the problems you encountered re VS2010 and VS2012 sharing Your issue pertaining to your include and library directories and so forth. Have you looked into creating your own Property Sheets instead of editing Microsoft.Cpp.Win32.User or Microsoft.Cpp.x64.User directly? This way you can set specific properties per solution/project and keep things separate if so required.

Alternatively properties that are not specific to a solution can be shared by loading the same Property Sheet in the various projects where required.

I suspect this would avoid the problems you encountered re VS2010 and VS2012 sharing

]]>