update 2015 docs

BrianPeekMSFT · BrianPeekMSFT · commit 773cc5142bc0 · 2017-03-03T21:24:16.000-05:00
diff --git a/docs/ide/working-with-project-properties.md b/docs/ide/working-with-project-properties.md
@@ -75,7 +75,8 @@ In the IDE, all information that is needed to build a project is exposed as
  The                  **Any CPU** target platform value that you might see in                  **Configuration Manager** has no effect on native C++ projects; it is relevant for C++/CLI and other .NET project types. For more information, see                  [/CLRIMAGETYPE (Specify Type of CLR Image)](../build/reference/clrimagetype-specify-type-of-clr-image.md).  
   
 ## Property pages  
- As stated earlier, the Visual C++ project system is based on                  [MSBuild](/visualstudio/msbuild/msbuild-properties) and the values are stored in the XML project file, default .props and .targets files that (for Visual Studio 2015) are located in                     **\<drive>\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140** and in custom .props files that you might add. We highly recommend that you use NOT edit those files manually, and instead use the property pages in the IDE  to modify all properties, especially those that participate in inheritance, unless you have a very good understanding of MSBuild.  
+ As stated earlier, the Visual C++ project system is based on                  [MSBuild](/visualstudio/msbuild/msbuild-properties) and the values are stored in the XML project file, default .props and .targets files.  For Visual Studio 2015, these files are located in                     **\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140**.  For Visual Studio 2017, these files are located in **\\Program Files (x86)\\Microsoft Visual Studio\\2017\\_edition_\\Common7\\IDE\\VC\\VCTargets**
+ , where _edition_ is the Visual Studio edition installed. Properties are also stored in any  custom .props files that you might add to your own project. We highly recommend that you NOT edit those files manually, and instead use the property pages in the IDE to modify all properties, especially those that participate in inheritance, unless you have a very good understanding of MSBuild.  
   
  The following illustration shows the property pages for a Visual C++ project. In the left pane, the                  **VC++ Directories***rule* is selected, and the right pane lists the properties that are associated with that rule. The                  `$(...)` values are unfortunately called                  *macros*. These are                  *not* C/C++ macros but simply compile-time constants. Macros are discussed in the                  [Property page macros](#bkmkPropertiesVersusMacros) section later in this article.)  
   
