Vs project property sheet

vs project property sheet
as projects in a solution grow more and more, the project setting management will be more and more complicated. modifying one by one will be hard work and easy to cause mistakes. luckily, VS has already provides us a way to manage such area work by "Property Manager" which can create/edit finally manage "project property sheet" thing.

1. several Concepts
-- Project property sheet
A project property sheet is. XML file with the extension. vsprops. you can use property sheets to create project deployments that can be applied to multiple projects since project settings that are defined in. vsprops files are inheritable, unlike project settings defined in project files (. vcproj files ). therefore, a project configuration defined in. vcproj file can inherit Project Settings from one or more property sheets (. vsprops files ).
-- User-Defined macros
we will always see a lot of predefined macros like $ (solution), $ (outdir ). we can define ours by project property sheet. there is a "User macros" there. they are defined in. vsprops files directly.
Note: there are actually two ways to define user-defined macros: one is described as above; the other is to define them directly as environment variables.

2. How to use a project property sheet
1) create one. Use property manager.
2) In every C ++ project setting's general area, there is a "inherited project property sheets", where we can specify those. vsprops files to inherit from.
3) to inherit the settings: For those setting which can have only one input like "output directory", you can choose "inherit from parent or project defaults" directly; for those settings which can have multiply inputs like "Additional include directory", the inheritance is done automatically.

In a word, for a solution, if preparing well A. vsprops to contain common settings, and let it be inherited by its projects, we can manage Project Settings easily!

Note this article into blog: http://www.itwis.com/html/c/ctool/20070904/1.html