Merge pull request #2481 from v-thepet/msbuild2

MBuild PR #7

Author: TrishaMc

docs/msbuild/how-to-select-the-files-to-build.md

@@ -15,10 +15,10 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# How to: Select the Files to Build
+# How to: Select the files to build
 When you build a project that contains several files, you can list each file separately in the project file, or you can use wildcards to include all the files in one directory or a nested set of directories.  
 
-## Specifying Inputs  
+## Specify inputs  
  Items represent the inputs for a build. For more information on items, see [Items](../msbuild/msbuild-items.md).  
 
  To include files for a build, they must be included in an item list in the [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] project file. Multiple files can be added to item lists by either including the files individually or using wildcards to include many files at once.  
@@ -29,7 +29,7 @@ When you build a project that contains several files, you can list each file sep
 
      `<CSFile Include="form1.cs"/>`  
 
-     - or -  
+     or 
 
      `<VBFile Include="form1.vb"/>`  
 
@@ -42,44 +42,44 @@ When you build a project that contains several files, you can list each file sep
 
      `<CSFile Include="form1.cs;form2.cs"/>`  
 
-     - or -  
+     or 
 
      `<VBFile Include="form1.vb;form2.vb"/>`  
 
-## Specifying Inputs with Wildcards  
+## Specify inputs with wildcards  
  You can also use wildcards to recursively include all files or only specific files from subdirectories as inputs for a build. For more information about wildcards, see [Items](../msbuild/msbuild-items.md)  
 
- The following examples are based on a project that contains graphics files in the following directories and subdirectories, with the project file located in the Project directory:  
+ The following examples are based on a project that contains graphics files in the following directories and subdirectories, with the project file located in the *Project* directory:  
 
- Project\Images\BestJpgs  
+ *Project\Images\BestJpgs*  
 
- Project\Images\ImgJpgs  
+ *Project\Images\ImgJpgs*  
 
- Project\Images\ImgJpgs\Img1  
+ *Project\Images\ImgJpgs\Img1*  
 
-#### To include all .jpg files in the Images directory and subdirectories  
+#### To include all *.jpg* files in the *Images* directory and subdirectories  
 
 -   Use the following `Include` attribute:  
 
      `Include="Images\**\*.jpg"`  
 
-#### To include all .jpg files starting with "img"  
+#### To include all *.jpg* files starting with *img*  
 
 -   Use the following `Include` attribute:  
 
      `Include="Images\**\img*.jpg"`  
 
-#### To include all files in directories with names ending in "jpgs"  
+#### To include all files in directories with names ending in *jpgs*  
 
 -   Use one of the following `Include` attributes:  
 
      `Include="Images\**\*jpgs\*.*"`  
 
-     - or -  
+     or
 
      `Include="Images\**\*jpgs\*"`  
 
-## Passing Items to a Task  
+## Pass items to a task  
  In a project file, you can use the @() notation in tasks to specify an entire item list as the input for a build. You can use this notation whether you list all files separately or use wildcards.  
 
 #### To use all Visual C# or Visual Basic files as inputs  
@@ -88,12 +88,12 @@ When you build a project that contains several files, you can list each file sep
 
      `<CSC Sources="@(CSFile)">...</CSC>`  
 
-     - or -  
+     or 
 
      `<VBC Sources="@(VBFile)">...</VBC>`  
 
 > [!NOTE]
->  You must use wildcards with items to specifiy the inputs for a build; you cannot specify the inputs using the `Sources` attribute in [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] tasks such as [Csc](../msbuild/csc-task.md) or [Vbc](../msbuild/vbc-task.md). The following example is not valid in a project file:  
+>  You must use wildcards with items to specify the inputs for a build; you cannot specify the inputs using the `Sources` attribute in [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] tasks such as [Csc](../msbuild/csc-task.md) or [Vbc](../msbuild/vbc-task.md). The following example is not valid in a project file:  
 >   
 >  `<CSC Sources="*.cs">...</CSC>`  
   
@@ -132,7 +132,7 @@ When you build a project that contains several files, you can list each file sep
 ```  
 
 ## Example  
- The following code example uses a wildcard to include all the .cs files.  
+ The following code example uses a wildcard to include all the *.cs* files.  
 
 ```xml  
 <Project DefaultTargets="Compile"  
@@ -165,6 +165,6 @@ When you build a project that contains several files, you can list each file sep
 </Project>  
 ```  
 
-## See Also  
- [How to: Exclude Files from the Build](../msbuild/how-to-exclude-files-from-the-build.md)   
- [Items](../msbuild/msbuild-items.md)
+## See also  
+ [How to: Exclude files from the build](../msbuild/how-to-exclude-files-from-the-build.md)   
+ [Items](../msbuild/msbuild-items.md)

docs/msbuild/how-to-specify-which-target-to-build-first.md

@@ -15,10 +15,10 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# How to: Specify Which Target to Build First
+# How to: Specify which target to build first
 A project file can contain one or more `Target` elements that define how the project is built. The [!INCLUDE[vstecmsbuildengine](../msbuild/includes/vstecmsbuildengine_md.md)] ([!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)]) engine builds the first project it finds, and any dependencies, unless the project file contains a `DefaultTargets` attribute, an `InitialTargets` attribute, or a target is specified at the command line using the **/target** switch.  
 
-## Using the InitialTargets Attribute  
+## Use the InitialTargets attribute  
  The `InitialTargets` attribute of the `Project` element specifies a target that will run first, even if targets are specified on the command line or in the `DefaultTargets` attribute.  
 
 #### To specify one initial target  
@@ -35,7 +35,7 @@ A project file can contain one or more `Target` elements that define how the pro
 
      `<Project InitialTargets="Clean;Compile">`  
 
-## Using the DefaultTargets Attribute  
+## Use the DefaultTargets attribute  
  The `DefaultTargets` attribute of the `Project` element specifies which target or targets are built if a target is not specified explicitly on the command line. If targets are specified in both the `InitialTargets` and `DefaultTargets` attributes and no target is specified on the command line, [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] runs the targets specified in the `InitialTargets` attribute followed by the targets specified in the `DefaultTargets` attribute.  
 
 #### To specify one default target  
@@ -52,7 +52,7 @@ A project file can contain one or more `Target` elements that define how the pro
 
      `<Project DefaultTargets="Clean;Compile">`  
 
-## Using the /target Switch  
+## Use the /target Switch  
  If a default target is not defined in the project file, or if you do not want to use that default target, you can use the command line switch **/target** to specify a different target. The target or targets specified with the **/target** switch are run instead of the targets specified by the `DefaultTargets` attribute. Targets specified in the `InitialTargets` attribute always run first.  
 
 #### To use a target other than the default target first  
@@ -67,7 +67,7 @@ A project file can contain one or more `Target` elements that define how the pro
 
      `msbuild <file name>.proj /t:Clean;Compile`  
 
-## See Also
+## See also
   [MSBuild](../msbuild/msbuild.md)  
  [Targets](../msbuild/msbuild-targets.md)   
- [How to: Clean a Build](../msbuild/how-to-clean-a-build.md)
+ [How to: Clean a build](../msbuild/how-to-clean-a-build.md)

docs/msbuild/how-to-use-environment-variables-in-a-build.md

@@ -15,10 +15,10 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# How to: Use Environment Variables in a Build
+# How to: Use environment variables in a build
 When you build projects, it is often necessary to set build options using information that is not in the project file or the files that comprise your project. This information is typically stored in environment variables.  
 
-## Referencing Environment Variables  
+## Reference environment variables  
  All environment variables are available to the [!INCLUDE[vstecmsbuildengine](../msbuild/includes/vstecmsbuildengine_md.md)] ([!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)]) project file as properties.  
 
 > [!NOTE]
@@ -34,7 +34,7 @@ When you build projects, it is often necessary to set build options using inform
 
 #### To provide a default value for a property  
 
--   Use a `Condition` attribute on a property to set the value only if the property has no value. For example, the following code sets the `ToolsPath` property to c:\tools only if the `ToolsPath` environment variable is not set:  
+-   Use a `Condition` attribute on a property to set the value only if the property has no value. For example, the following code sets the `ToolsPath` property to *c:\tools* only if the `ToolsPath` environment variable is not set:  
 
      `<ToolsPath Condition="'$(TOOLSPATH)' == ''">c:\tools</ToolsPath>`  
 
@@ -58,7 +58,7 @@ When you build projects, it is often necessary to set build options using inform
 </Project>  
 ```  
 
-## See Also  
+## See also  
 [MSBuild ](../msbuild/msbuild.md)  
-[MSBuild Properties](../msbuild/msbuild-properties.md)  
-[How to: Build the Same Source Files with Different Options](../msbuild/how-to-build-the-same-source-files-with-different-options.md)  
+[MSBuild properties](../msbuild/msbuild-properties.md)  
+[How to: Build the same source files with different options](../msbuild/how-to-build-the-same-source-files-with-different-options.md)  

docs/msbuild/how-to-use-project-sdk.md

@@ -12,7 +12,7 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# How to: Use MSBuild Project SDKs
+# How to: Use MSBuild project SDKs
 
 [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] 15.0 introduced the concept of the "project SDK", which simplifies using software development kits that require properties and targets to be imported.
 
@@ -40,9 +40,9 @@ During evaluation of the project, [!INCLUDE[vstecmsbuild](../extensibility/inter
 </Project>
 ```
 
-## Referencing a Project SDK
+## Reference a project SDK
 
- There are three ways to reference a project SDK
+ There are three ways to reference a project SDK:
 
 1. Use the `Sdk` attribute on the `<Project/>` element:
 
@@ -82,7 +82,7 @@ During evaluation of the project, [!INCLUDE[vstecmsbuild](../extensibility/inter
 
    When using the `<Import/>` element, you can specify an optional `Version` attribute as well.  For example, you can specify `<Import Project="Sdk.props" Sdk="My.Custom.Sdk" Version="1.2.3" />`.
 
-## How Project SDKs are Resolved
+## How project SDKs are resolved
 
 When evaluating the import, [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] dynamically resolves the path to the project SDK based on the name and version you specified.  [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] also has a list of registered SDK resolvers which are plug-ins that locate project SDKs on your machine.  These plug-ins include:
 
@@ -103,11 +103,11 @@ The NuGet-based SDK resolver supports specifying a version in your [global.json]
 }
 ```
 
-Only one version of each project SDK can be used during a build.  If you are referencing two different versions of the same project SDK, MSBuild will emit a warning.  It is recommended to **not** specify a version in your projects if a version is specified in your `global.json`.  
+Only one version of each project SDK can be used during a build.  If you are referencing two different versions of the same project SDK, MSBuild will emit a warning.  It is recommended to **not** specify a version in your projects if a version is specified in your *global.json*.  
 
-## See Also
+## See also
 
- [MSBuild Concepts](../msbuild/msbuild-concepts.md)   
- [Customize Your Build](../msbuild/customize-your-build.md)   
- [Packages, Metadata, and Frameworks](/dotnet/core/packages)   
+ [MSBuild concepts](../msbuild/msbuild-concepts.md)   
+ [Customize your build](../msbuild/customize-your-build.md)   
+ [Packages, metadata, and frameworks](/dotnet/core/packages)   
  [Additions to the csproj format for .NET Core](/dotnet/core/tools/csproj)

docs/msbuild/how-to-use-reserved-xml-characters-in-project-files.md

@@ -14,10 +14,10 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# How to: Use Reserved XML Characters in Project Files
+# How to: Use reserved XML characters in project files
 When you author project files, you might need to use reserved XML characters, for example, in property values or in task parameter values. However, some reserved characters must be replaced by a named entity so that the project file can be parsed.  
 
-## Using Reserved Characters  
+## Use reserved characters  
  The following table describes the reserved XML characters that must be replaced by the corresponding named entity so that the project file can be parsed.  
 
 |Reserved character|Named entity|  
@@ -66,6 +66,6 @@ When you author project files, you might need to use reserved XML characters, fo
 </Project>  
 ```  
 
-## See Also  
- [MSBuild Reference](../msbuild/msbuild-reference.md)    
+## See also  
+ [MSBuild reference](../msbuild/msbuild-reference.md)    
  [MSBuild](../msbuild/msbuild.md)    

docs/msbuild/how-to-use-the-same-target-in-multiple-project-files.md

@@ -14,11 +14,11 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# How to: Use the Same Target in Multiple Project Files
+# How to: Use the same target in multiple project files
 If you have authored several [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] project files, you might have discovered that you need to use the same tasks and targets in different project files. Instead of including the complete description of those tasks or targets in every project file, you can save a target in a separate project file and then import that project into any other project that needs to use the target.  
 
-## Using the Import Element  
- The `Import` element is used to insert one project file into another project file. The project file that is being imported must be a valid [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] project file and contain well-formed XML. The `Project` attribute specifies the path to the imported project file. For more information on the `Import` element, see [Import Element (MSBuild)](../msbuild/import-element-msbuild.md).  
+## Use the Import element  
+ The `Import` element is used to insert one project file into another project file. The project file that is being imported must be a valid [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] project file and contain well-formed XML. The `Project` attribute specifies the path to the imported project file. For more information on the `Import` element, see [Import element (MSBuild)](../msbuild/import-element-msbuild.md).  
 
 #### To import a project  
 
@@ -30,10 +30,10 @@ If you have authored several [!INCLUDE[vstecmsbuild](../extensibility/internals/
 
 3.  Following the `Import` element, define all properties and items that must override default definitions of properties and items in the imported project.  
 
-## Order of Evaluation  
+## Order of evaluation  
  When [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] reaches an `Import` element, the imported project is effectively inserted into the importing project at the location of the `Import` element. Therefore, the location of the `Import` element can affect the values of properties and items. It is important to understand the properties and items that are set by the imported project, and the properties and items that the imported project uses.  
 
- When the project builds, all properties are evaluated first, followed by items. For example, the following XML defines the imported project file MyCommon.targets:  
+ When the project builds, all properties are evaluated first, followed by items. For example, the following XML defines the imported project file *MyCommon.targets*:  
 
 ```xml  
 <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">  
@@ -47,7 +47,7 @@ If you have authored several [!INCLUDE[vstecmsbuild](../extensibility/internals/
 </Project>  
 ```  
 
- The following XML defines MyApp.proj, which imports MyCommon.targets:  
+ The following XML defines *MyApp.proj*, which imports *MyCommon.targets*:  
 
 ```xml  
 <Project  
@@ -64,7 +64,7 @@ If you have authored several [!INCLUDE[vstecmsbuild](../extensibility/internals/
 
  `Name="MyCommon"`  
 
- Because the project is imported after the property `Name` has been defined in MyApp.proj, the definition of `Name` in MyCommon.targets overrides the definition in MyApp.proj. If, the project is imported before the property Name is defined, the build would display the following message:  
+ Because the project is imported after the property `Name` has been defined in *MyApp.proj*, the definition of `Name` in *MyCommon.targets* overrides the definition in *MyApp.proj*. If the project is imported before the property Name is defined, the build would display the following message:  
 
  `Name="MyApp"`  
 
@@ -77,7 +77,7 @@ If you have authored several [!INCLUDE[vstecmsbuild](../extensibility/internals/
 3.  Define in the project file all properties and items that must override default definitions of properties and items in the imported project.  
 
 ## Example  
- The following code example shows the MyCommon.targets file that the second code example imports. The .targets file evaluates properties from the importing project to configure the build.  
+ The following code example shows the *MyCommon.targets* file that the second code example imports. The *.targets* file evaluates properties from the importing project to configure the build.  
 
 ```xml  
 <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">  
@@ -95,7 +95,7 @@ If you have authored several [!INCLUDE[vstecmsbuild](../extensibility/internals/
 ```  
 
 ## Example  
- The following code example imports the MyCommon.targets file.  
+ The following code example imports the *MyCommon.targets* file.  
 
 ```xml  
 <Project DefaultTargets="Build"  
@@ -107,6 +107,6 @@ If you have authored several [!INCLUDE[vstecmsbuild](../extensibility/internals/
 </Project>  
 ```  
 
-## See Also  
- [Import Element (MSBuild)](../msbuild/import-element-msbuild.md)   
+## See also  
+ [Import element (MSBuild)](../msbuild/import-element-msbuild.md)   
  [Targets](../msbuild/msbuild-targets.md)