updated path info for vs2017 (#255)

* updated path info for vs2017

* Update how-to-integrate-custom-tools-into-the-project-properties.md

added text explaining LCID and VS Edition in path

* Update how-to-integrate-custom-tools-into-the-project-properties.md

one more 1033 tweak

Author: mikeblome

docs/build/how-to-integrate-custom-tools-into-the-project-properties.md

@@ -1,7 +1,7 @@
 ---
 title: "How to: Integrate Custom Tools into the Project Properties | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "04/27/2016"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -45,17 +45,17 @@ You can add custom tool options to the Visual Studio **Property Pages** window b
 
 1.  In the XML editor, create an XML file.  
 
-2.  Save the file in the %ProgramFiles%\MSBuild\Microsoft.Cpp\v4.0\ folder. Every rule in the **Property Pages** window is represented by an XML file in this folder. Make sure that the file is uniquely named in the folder.  
+2.  Save the file in the Visual Studio 2017 `VCTargets\1033` folder. You will have a different path for each edition of Visual Studio 2017 that is installed and each language. For example, the folder path for Visual Studio Enterprise edition in English is `%ProgramFiles%\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\1033`. Adjust the path for your language and Visual Studio edition. Every rule in the **Property Pages** window is represented by an XML file in this folder. Make sure that the file is uniquely named in the folder.  
 
-3.  Copy the content of %ProgramFiles%\MSBuild\Microsoft.Cpp\v4.0\cl.xml, close it without saving changes, and then paste the content in your new XML file. You can use any XML schema file - this is just one that can be used so you start with a template.  
+3.  Copy the content of  `%ProgramFiles%\Microsoft Visual Studio\2017\<VS Edition>\Common7\IDE\VC\VCTargets\<LCID>\cl.xml`, close it without saving changes, and then paste the content in your new XML file. You can use any XML schema file - this is just one that can be used so you start with a template.  
 
 4.  In the new XML file, modify the content according to your requirements. Make sure to change the **Rule Name** and **Rule.DisplayName** at the top of the file.  
 
 5.  Save the changes and close the file.  
 
-6.  The XML files in %ProgramFiles%\MSBuild\Microsoft.Cpp\v4.0\ are loaded when Visual Studio starts. Therefore, to test the new file, restart Visual Studio.  
+6.  The XML files in `%ProgramFiles%\Microsoft Visual Studio\2017\<VS Edition>\Common7\IDE\VC\VCTargets\<LCID>` are loaded when Visual Studio starts. Therefore, to test the new file, restart Visual Studio.  
 
 7.  In **Solution Explorer**, right-click a project and then click **Properties**. In the **Property Pages** window, in the left pane, verify that there is a new node with the name of your Rule.  
 
 ## See Also  
- [MSBuild (Visual C++)](../build/msbuild-visual-cpp.md)
+ [MSBuild (Visual C++)](../build/msbuild-visual-cpp.md)