Merge pull request #1357 from MicrosoftDocs/mikejo-msbld

Refresh msbuild docs

Author: Mikejo5000

docs/msbuild/msbuild-toolset-toolsversion.md

@@ -1,7 +1,7 @@
 ---
 title: "MSBuild Toolset (ToolsVersion) | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "01/31/2018"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: msbuild
@@ -13,7 +13,6 @@ helpviewer_keywords:
   - "MSBuild, targeting a specific .NET framework"
   - "multitargeting [MSBuild]"
 ms.assetid: 40040ee7-4620-4043-a6d8-ccba921421d1
-caps.latest.revision: 30
 author: Mikejo5000
 ms.author: mikejo
 manager: ghogen
@@ -28,7 +27,10 @@ MSBuild uses a Toolset of tasks, targets, and tools to build an application. Typ
 
 ```xml  
 <Project ToolsVersion="15.0" ... </Project>  
-```  
+``` 
+
+> [!NOTE] 
+> Some project types use the `sdk` attribute instead of `ToolsVersion`. For more information, see [Packages, Metadata, and Frameworks](/dotnet/core/packages) and [Additions to the csproj format for .NET Core](/dotnet/core/tools/csproj).
   
 ## How the ToolsVersion Attribute Works  
  When you create a project in Visual Studio, or upgrade an existing project, an attribute named `ToolsVersion` is automatically included in the project file and its value corresponds to the version of MSBuild that is included in the Visual Studio edition. For more information, see [Targeting a Specific .NET Framework Version](../ide/targeting-a-specific-dotnet-framework-version.md).  
@@ -68,7 +70,7 @@ MSBuild uses a Toolset of tasks, targets, and tools to build an application. Typ
 
 -   By using <xref:Microsoft.Build.Utilities.ToolLocationHelper> methods  
 
- Toolset properties specify the paths of the tools. MSBuild uses the value of the `ToolsVersion` attribute in the project file to locate the corresponding registry key, and then uses the information in the registry key to set the Toolset properties. For example, if `ToolsVersion` has the value `12.0`, then MSBuild sets the Toolset properties according to this registry key: HKLM\Software\Microsoft\MSBuild\ToolsVersions\12.0.  
+ Toolset properties specify the paths of the tools. Starting in Visual Studio 2017, MSBuild no longer has a fixed location. By default, it is located in the MSBuild\15.0\Bin folder relative to the Visual Studio installation location. In earlier versions, MSBuild uses the value of the `ToolsVersion` attribute in the project file to locate the corresponding registry key, and then uses the information in the registry key to set the Toolset properties. For example, if `ToolsVersion` has the value `12.0`, then MSBuild sets the Toolset properties according to this registry key: HKLM\Software\Microsoft\MSBuild\ToolsVersions\12.0.  
 
  These are Toolset properties:  
 
@@ -91,7 +93,7 @@ MSBuild uses a Toolset of tasks, targets, and tools to build an application. Typ
 -   <xref:Microsoft.Build.Utilities.ToolLocationHelper.GetPathToBuildTools%2A> returns the path of the build tools.  
 
 ### Sub-toolsets  
- As described earlier in this topic, MSBuild uses a registry key to specify the path of the basic tools. If the key has a subkey, MSBuild uses it to specify the path of a sub-toolset that contains additional tools. In this case, the Toolset is defined by combining the property definitions that are defined in both keys.  
+ For versions MSBuild prior to 15.0, MSBuild uses a registry key to specify the path of the basic tools. If the key has a subkey, MSBuild uses it to specify the path of a sub-toolset that contains additional tools. In this case, the Toolset is defined by combining the property definitions that are defined in both keys.  
 
 > [!NOTE]
 >  If toolset property names collide, the value that's defined for the subkey path overrides the value that's defined for the root key path.  
@@ -102,7 +104,7 @@ MSBuild uses a Toolset of tasks, targets, and tools to build an application. Typ
 
 -   "11.0" specifies the .NET Framework 4.5 sub-toolset  
 
--   "12.0" specifies the .NET Framework 4.5.1 sub-toolset  
+-   "12.0" specifies the .NET Framework 4.5.1 sub-toolset 
 
  Sub-toolsets 10.0 and 11.0 should be used with ToolsVersion 4.0. In later versions, the sub-toolset version and the ToolsVersion should match.  
 

docs/msbuild/standard-and-custom-toolset-configurations.md

@@ -1,7 +1,7 @@
 ---
 title: "Standard and Custom Toolset Configurations | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "01/31/2018"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: msbuild
@@ -11,7 +11,6 @@ helpviewer_keywords:
   - "MSBuild, custom toolset configurations"
   - "MSBuild, msbuild.exe.config"
 ms.assetid: 15a048c8-5ad3-448e-b6e9-e3c5d7147ed2
-caps.latest.revision: 31
 author: Mikejo5000
 ms.author: mikejo
 manager: ghogen
@@ -22,30 +21,27 @@ ms.workload:
 An MSBuild Toolset contains references to tasks, targets, and tools that you can use to build an application project. MSBuild includes a standard Toolset, but you can also create custom Toolsets. For information about how to specify a Toolset, see [Toolset (ToolsVersion)](../msbuild/msbuild-toolset-toolsversion.md)  
 
 ## Standard Toolset Configurations  
- MSBuild 12.0 includes the following standard Toolsets:  
+ MSBuild 15.0 includes the following standard Toolsets:  
 
 |ToolsVersion|Toolset Path (as specified in the MSBuildToolsPath or MSBuildBinPath build property)|  
 |------------------|--------------------------------------------------------------------------------------------|  
 |2.0|*Windows installation path*\Microsoft.Net\Framework\v2.0.50727\|  
 |3.5|*Windows installation path*\Microsoft.NET\Framework\v3.5\|  
 |4.0|*Windows installation path*\Microsoft.NET\Framework\v4.0.30319\|  
-|12.0|*%ProgramFiles%*\MSBuild\12.0\bin|  
+|15.0|*Visual Studio installation path*\MSBuild\15.0\bin|  
 
- The `ToolsVersion` value determines which Toolset is used by a project that Visual Studio generates. In [!INCLUDE[vs_dev12](../extensibility/includes/vs_dev12_md.md)] the default value is "12.0" (no matter what the version specified in the project file), but you can override that attribute by using the **/toolsversion** switch at a command prompt. For information about this attribute and other ways to specify the `ToolsVersion`, see [Overriding ToolsVersion Settings](../msbuild/overriding-toolsversion-settings.md).  
+ The `ToolsVersion` value determines which Toolset is used by a project that Visual Studio generates. In Visual Studio 2017, the default value is "15.0" (no matter what the version specified in the project file), but you can override that attribute by using the **/toolsversion** switch at a command prompt. For information about this attribute and other ways to specify the `ToolsVersion`, see [Overriding ToolsVersion Settings](../msbuild/overriding-toolsversion-settings.md).  
 
- If the `ToolsVersion` isn't specified, the registry key **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\\<Version Number\>\DefaultToolsVersion** defines the `ToolsVersion`, which is always 2.0.  
-  
- The following registry keys specify the installation path of MSBuild.exe.  
+ Visual Studio 2017 does not use a registry key for the path to MSBuild. For versions of MSBuild prior to 15.0 that are installed with Visual Studio 2017, the following registry keys specify the installation path of MSBuild.exe.  
 
 |Registry Key|Key Name|String Key Value|  
 |------------------|--------------|----------------------|  
 |\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\2.0\|MSBuildToolsPath|.NET Framework 2.0 Install Path|  
 |\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSBuild\ToolsVersions\3.5\|MSBuildToolsPath|.NET Framework 3.5 Install Path|  
 |\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSBuild\ToolsVersions\4.0\|MSBuildToolsPath|.NET Framework 4 Install Path|  
-|\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSBuild\ToolsVersions\12.0\|MSBuildToolsPath|MSBuild Install Path|  
 
 ### Sub-toolsets  
- If the registry key in the previous table has a subkey, MSBuild uses it to determine the path of a sub-toolset may override the path in the parent toolset. The following subkey is an example:  
+ If the registry key in the previous table has a subkey, MSBuild uses it to determine the path of a sub-toolset that overrides the path in the parent toolset. The following subkey is an example:  
 
  \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\12.0\12.0  
 
@@ -59,11 +55,11 @@ An MSBuild Toolset contains references to tasks, targets, and tools that you can
 ## Custom Toolset Definitions  
  When a standard Toolset does not fulfill your build requirements, you can create a custom Toolset. For example, you may have a build lab scenario in which you must have a separate system for building [!INCLUDE[vcprvc](../code-quality/includes/vcprvc_md.md)] projects. By using a custom Toolset, you can assign custom values to the `ToolsVersion` attribute when you create projects or run MSBuild.exe. By doing this, you can also use the `$(MSBuildToolsPath)` property to import .targets files from that directory, as well as defining your own custom toolset properties that can be used for any project that uses that toolset.  
 
- Specify a custom Toolset in the configuration file for MSBuild.exe (or for the custom tool that hosts the MSBuild engine if that is what you are using). For example, the configuration file for MSBuild.exe could include the following Toolset definition if you wished to override the default behavior of ToolsVersion 12.0.  
+ Specify a custom Toolset in the configuration file for MSBuild.exe (or for the custom tool that hosts the MSBuild engine if that is what you are using). For example, the configuration file for MSBuild.exe could include the following Toolset definition if you wished to override the default behavior of ToolsVersion 15.0.  
 
 ```xml  
-<msbuildToolsets default="12.0">  
-   <toolset toolsVersion="12.0">  
+<msbuildToolsets default="15.0">  
+   <toolset toolsVersion="15.0">  
       <property name="MSBuildToolsPath"   
         value="C:\SpecialPath" />  
    </toolset>  
@@ -76,7 +72,7 @@ An MSBuild Toolset contains references to tasks, targets, and tools that you can
 <configSections>  
    <section name="msbuildToolsets"         
        Type="Microsoft.Build.BuildEngine.ToolsetConfigurationSection,   
-       Microsoft.Build.Engine, Version=12.0.0.0, Culture=neutral,   
+       Microsoft.Build.Engine, Version=15.1.0.0, Culture=neutral,   
        PublicKeyToken=b03f5f7f11d50a3a"  
    </section>  
 </configSections>  

docs/msbuild/walkthrough-using-msbuild.md

@@ -10,7 +10,6 @@ ms.topic: "article"
 helpviewer_keywords: 
   - "MSBuild, tutorial"
 ms.assetid: b8a8b866-bb07-4abf-b9ec-0b40d281c310
-caps.latest.revision: 32
 author: Mikejo5000
 ms.author: mikejo
 manager: ghogen
@@ -57,45 +56,33 @@ MSBuild is the build platform for Microsoft and Visual Studio. This walkthrough
      The project file appears in the code editor.  
 
 ## Targets and Tasks  
- Project files are XML-formatted files with the root node [Project](../msbuild/project-element-msbuild.md).  
+Project files are XML-formatted files with the root node [Project](../msbuild/project-element-msbuild.md).  
 
 ```xml  
 <?xml version="1.0" encoding="utf-8"?>  
-<Project ToolsVersion="12.0" DefaultTargets="Build"  xmlns="http://schemas.microsoft.com/developer/msbuild/2003">  
+<Project ToolsVersion="15.0"  xmlns="http://schemas.microsoft.com/developer/msbuild/2003">  
 ```  
 
- You must specify the xmlns namespace in the Project element.  
+You must specify the xmlns namespace in the Project element. If `ToolsVersion` is present in a new project, it must be "15.0".
 
- The work of building an application is done with [Target](../msbuild/target-element-msbuild.md) and [Task](../msbuild/task-element-msbuild.md) elements.  
+The work of building an application is done with [Target](../msbuild/target-element-msbuild.md) and [Task](../msbuild/task-element-msbuild.md) elements.  
 
 -   A task is the smallest unit of work, in other words, the "atom" of a build. Tasks are independent executable components which may have inputs and outputs. There are no tasks currently referenced or defined in the project file. You add tasks to the project file in the sections below. For more information, see the [Tasks](../msbuild/msbuild-tasks.md) topic.  
 
--   A target is a named sequence of tasks. There are two targets at the end of the project file that are currently enclosed in HTML comments: BeforeBuild and AfterBuild.  
+-   A target is a named sequence of tasks. For more information, see the [Targets](../msbuild/msbuild-targets.md) topic.  
 
-    ```xml  
-    <Target Name="BeforeBuild">  
-    </Target>  
-    <Target Name="AfterBuild">  
-    </Target>  
-    ```  
-  
-     For more information, see the [Targets](../msbuild/msbuild-targets.md) topic.  
-  
- The Project node has an optional DefaultTargets attribute that selects the default target to build, in this case Build.  
-  
-```xml  
-<Project ToolsVersion="12.0" DefaultTargets="Build" ...  
-```  
-  
- The Build target is not defined in the project file. Instead, it is imported from the file Microsoft.CSharp.targets by using the [Import](../msbuild/import-element-msbuild.md) element.  
+The default target is not defined in the project file. Instead, it is specified in imported projects. The [Import](../msbuild/import-element-msbuild.md) element specifies imported projects. For example, in a C# project, the default target is imported from the file Microsoft.CSharp.targets. 
 
 ```xml  
 <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />  
 ```  
 
- Imported files are effectively inserted into the project file wherever they are referenced.  
+Imported files are effectively inserted into the project file wherever they are referenced.  
+
+> [!NOTE]
+> Some project types, such as .NET Core, use a simplified schema with an `Sdk` attribute instead of `ToolsVersion`. These projects have implicit imports and different default attribute values.
   
- MSBuild keeps track of the targets of a build, and guarantees that each target is built no more than once.  
+MSBuild keeps track of the targets of a build, and guarantees that each target is built no more than once.  
 
 ## Adding a Target and a Task  
  Add a target to the project file. Add a task to the target that prints out a message.  
@@ -155,9 +142,6 @@ MSBuild is the build platform for Microsoft and Visual Studio. This walkthrough
 
  By alternating between the code editor and the command window, you can change the project file and quickly see the results.  
 
-> [!NOTE]
->  If you run msbuild without the /t command switch, msbuild builds the target given by the DefaultTarget attribute of the Project element, in this case "Build". This builds the Windows Forms application BuildApp.exe.  
-  
 ## Build Properties  
  Build properties are name-value pairs that guide the build. Several build properties are already defined at the top of the project file:  
 
@@ -175,10 +159,10 @@ MSBuild is the build platform for Microsoft and Visual Studio. This walkthrough
  All properties are child elements of PropertyGroup elements. The name of the property is the name of the child element, and the value of the property is the text element of the child element. For example,  
 
 ```xml  
-<TargetFrameworkVersion>v12.0</TargetFrameworkVersion>  
+<TargetFrameworkVersion>v15.0</TargetFrameworkVersion>  
 ```  
 
- defines the property named TargetFrameworkVersion, giving it the string value "v12.0".  
+ defines the property named TargetFrameworkVersion, giving it the string value "v15.0".  
 
  Build properties may be redefined at any time. If  
 
@@ -220,7 +204,7 @@ $(PropertyName)
 
     ```  
     Configuration is Debug  
-    MSBuildToolsPath is C:\Program Files\MSBuild\12.0\bin  
+    MSBuildToolsPath is C:\Program Files (x86)\Microsoft Visual Studio\2017\<Visual Studio SKU>\MSBuild\15.0\Bin  
     ```  
 
 > [!NOTE]

docs/msbuild/what-s-new-in-msbuild-15-0.md

@@ -8,7 +8,6 @@ ms.technology: msbuild
 ms.tgt_pltfrm: ""
 ms.topic: "article"
 ms.assetid: 9976b6fd-d052-4017-b848-35b5bf4b2f66
-caps.latest.revision: 23
 author: Mikejo5000
 ms.author: mikejo
 manager: ghogen
@@ -35,7 +34,7 @@ MSBuild is now available as part of the [.NET Core SDK](https://www.microsoft.co
 -   The `SDK35ToolsPath` and `SDK40ToolsPath` properties point to the .NET Framework SDK that's packaged with this version of Visual Studio (for example, 10.0A for the 4.X tools).  
 
 ## Updates
-- [Project Element](../msbuild/project-element-msbuild.md) has a new `SDK` attribute. Also the `Xmlns` attribute is now optional.
+- [Project Element](../msbuild/project-element-msbuild.md) has a new `SDK` attribute. Also the `Xmlns` attribute is now optional. For more information, see [Packages, Metadata, and Frameworks](/dotnet/core/packages) and [Additions to the csproj format for .NET Core](/dotnet/core/tools/csproj).
 - [Item Element](../msbuild/item-element-msbuild.md) outside targets has a new `Update` attribute. Also, the restriction on the `Remove` attribute has been eliminated.
 - `Directory.Build.props` is a user-defined file that provides customizations to projects under a directory. This file is automatically imported from Microsoft.Common.props unless the property `ImportDirectoryBuildTargets` is set to **false**. `Directory.Build.targets` is imported by Microsoft.Common.targets.
 - Any metadata with a name that doesn't conflict with the current list of attributes can optionally be expressed as an attribute. For more information, see [Item Element](../msbuild/item-element-msbuild.md).