first draft

TylerMSFT · TylerMSFT · commit fb130b7af5bb · 2020-10-14T17:50:23.000-07:00
diff --git a/docs/build/projects-and-build-systems-cpp.md b/docs/build/projects-and-build-systems-cpp.md
@@ -54,41 +54,41 @@ You can invoke MSBuild from the command line by passing it a .vcxproj file along
 
 ## In This Section
 
-[Visual Studio projects](creating-and-managing-visual-cpp-projects.md)
+[Visual Studio projects](creating-and-managing-visual-cpp-projects.md)\
 How to create, configure, and build C++ projects in Visual Studio using its native build system (MSBuild).
 
-[CMake projects](cmake-projects-in-visual-studio.md)
+[CMake projects](cmake-projects-in-visual-studio.md)\
 How to code, build, and deploy CMake projects in Visual Studio.
 
-[Open Folder projects](open-folder-projects-cpp.md)
-How to use Visual Studio to code, build and deploy C++ projects based on any arbitrary build system, or no build system. at all.
+[Open Folder projects](open-folder-projects-cpp.md)\
+How to use Visual Studio to code, build and deploy C++ projects based on any arbitrary build system, or no build system at all.
 
-[Release builds](release-builds.md)
+[Release builds](release-builds.md)\
 How to create and troubleshoot optimized release builds for deployment to end users.
 
-[Use the MSVC toolset from the command line](building-on-the-command-line.md)<br/>
+[Use the MSVC toolset from the command line](building-on-the-command-line.md)\
 Discusses how to use the C/C++ compiler and build tools directly from the command line rather than using the Visual Studio IDE.
 
-[Building DLLs in Visual Studio](dlls-in-visual-cpp.md)
+[Building DLLs in Visual Studio](dlls-in-visual-cpp.md)\
 How to create, debug and deploy C/C++ DLLs (shared libraries) in Visual Studio.
 
-[Walkthrough: Creating and Using a Static Library](walkthrough-creating-and-using-a-static-library-cpp.md)
+[Walkthrough: Creating and Using a Static Library](walkthrough-creating-and-using-a-static-library-cpp.md)\
 How to create a .lib binary file.
 
-[Building C/C++ Isolated Applications and Side-by-side Assemblies](building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
+[Building C/C++ Isolated Applications and Side-by-side Assemblies](building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)\
 Describes the deployment model for Windows Desktop applications, based on the idea of isolated applications and side-by-side assemblies.
 
-[Configure C++ projects for 64-bit, x64 targets](configuring-programs-for-64-bit-visual-cpp.md)
+[Configure C++ projects for 64-bit, x64 targets](configuring-programs-for-64-bit-visual-cpp.md)\
 How to target 64-bit x64 hardware with the MSVC build tools.
 
-[Configure C++ projects for ARM processors](configuring-programs-for-arm-processors-visual-cpp.md)
+[Configure C++ projects for ARM processors](configuring-programs-for-arm-processors-visual-cpp.md)\
 How to use the MSVC build tools to target ARM hardware.
 
-[Optimizing Your Code](optimizing-your-code.md)
+[Optimizing Your Code](optimizing-your-code.md)\
 How to optimize your code in various ways including program guided optimizations.
 
-[Configuring Programs for Windows XP](configuring-programs-for-windows-xp.md)
+[Configuring Programs for Windows XP](configuring-programs-for-windows-xp.md)\
 How to target Windows XP with the MSVC build tools.
 
-[C/C++ Building Reference](reference/c-cpp-building-reference.md)<br/>
+[C/C++ Building Reference](reference/c-cpp-building-reference.md)\
 Provides links to reference articles about program building in C++, compiler and linker options, and various build tools.
diff --git a/docs/linux/configure-a-linux-project.md b/docs/linux/configure-a-linux-project.md
@@ -20,7 +20,7 @@ You can configure a Linux project to target a physical Linux machine, a virtual
 
 **Visual Studio 2019 version 16.1**:
 
-- When targeting WSL, you can avoid the copy operations that are necessary for building and IntelliSense when targeting remote Linux systems.
+- When you target WSL, you can avoid the copy operations needed to build and get IntelliSense that are required when you target a remote Linux system.
 
 - You can specify separate Linux targets for building and debugging.
 
@@ -34,6 +34,10 @@ To view configuration options, select the **Project > Properties** menu, or righ
 
 By default, an executable (.out) is built. To build a static or dynamic library, or to use an existing Makefile, use the **Configuration Type** setting.
 
+If you are building for Windows Subsystem for Linux (WSL), be aware that there are some differences between WSL version 1 and 2.
+- Version 1 is limited to 64 parallel compilation processes. This is goverened by the Max Parallel Compilation Jobs settings in **Configuration properties > C/C++ > General** (JTW LINK). 
+- If you intend to use more than 64 parallel compilation processes, we recommend that you build with Ninja, which generally will be faster and more reliable. This is governed by the **Enable Incremental Build** setting in **Configuration properties > General**.
+
 For more information about the settings in the property pages, see [Linux Project Property Page Reference](prop-pages-linux.md).
 
 ## Remote settings
diff --git a/docs/linux/create-a-new-linux-project.md b/docs/linux/create-a-new-linux-project.md
@@ -48,21 +48,24 @@ When you create a new C++ project for Linux in Visual Studio, you can choose to
 
 If you have an existing Windows Visual Studio solution that you would like to extend to compile for Linux, and CMake is not an option, then you can add a Visual Studio Linux project to the Windows solution, along with a **Shared Items** project. Put the code that is shared between both platforms in the Shared Items project, and add a reference to that project from the Windows and Linux projects.
 
-## To create a new Linux project
+## Create a new Linux project
 
 To create a new Linux project in Visual Studio 2019, follow these steps:
 
-1. Select **File > New Project** in Visual Studio, or press **Ctrl + Shift + N**.
-1. Set the **Language** to **C++** and search for "Linux". Select the project type to create, and then choose **Next**. Enter a **Name** and **Location**, and choose **Create**.
+1. Select **File > New Project** in Visual Studio, or press **Ctrl + Shift + N**. The Create a new project dialog appears.
+1. Set the language drop-down to **C++**.
+1. Set the platform drop-down to **Linux**.
+1. Select the project type to create, for example **Console Application**, and then choose **Next**. Enter a **Name** and **Location**, and choose **Create**.
 
-   ![Screenshot of the Add a new project dialog box with Linux typed in the search text box.](media/newproject-vs2019.png)
+   ![Screenshot of the new project dialog box with the language drop-down set to C++ and the platform drop-down set to Linux.](media/newproject-vs2019.png)
 
    | Project Type | Description |
    | ------------ | --- |
-   | **Blink (Raspberry)**           | Project targeted for a Raspberry Pi device, with sample code that blinks an LED |
-   | **Console Application (Linux)** | Project targeted for any Linux computer, with sample code that outputs text to the console |
-   | **Empty Project (Linux)**       | Project targeted for any Linux computer, with no sample code |
-   | **Makefile Project (Linux)**    | Project targeted for any Linux computer, built using a standard Makefile build system |
+   | **Raspberry Pi project** | Project targeted for a Raspberry Pi device, with sample code that blinks an LED |
+   | **Console Application** | Project targeted for any Linux computer, with sample code that outputs text to the console |
+   | **Empty Project** | Project targeted for any Linux computer, with no sample code |
+   | **Makefile Project** | Project targeted for any Linux computer, built using a standard Makefile build system |
+   | **CMake Project** | Project targeted for any Linux computer, built using the CMake build system |
 
 ## Next steps
 
diff --git a/docs/linux/download-install-and-setup-the-linux-development-workload.md b/docs/linux/download-install-and-setup-the-linux-development-workload.md
@@ -151,7 +151,7 @@ The target machine running Fedora uses the **dnf** package installer. To downloa
 
 You're now ready to create or open a Linux project and configure it to run on the target system. For more information, see:
 
-- [Create a new Linux project](create-a-new-linux-project.md)
+- [Create a new Linux MSBuild C++ project](create-a-new-linux-project.md)
 - [Configure a Linux CMake project](cmake-linux-project.md)
 
 ::: moniker-end
diff --git a/docs/linux/media/newproject-vs2019.png b/docs/linux/media/newproject-vs2019.png
diff --git a/docs/linux/prop-pages/c-cpp-linux.md b/docs/linux/prop-pages/c-cpp-linux.md
@@ -1,6 +1,6 @@
 ---
 title: "C/C++ Properties (Linux C++)"
-ms.date: "06/07/2019"
+ms.date: "10/14/2020"
 ms.assetid: 4bb8894b-c874-4a68-935e-b127d54e484f
 f1_keywords: []
 ---
@@ -30,6 +30,7 @@ Linux support is available in Visual Studio 2017 and later.
 | C++ Compiler | Specifies the program to invoke during compilation of C++ source files, or the path to the C++ compiler on the remote system. |
 | Compile Timeout | Remote compilation timeout, in milliseconds. |
 | Copy Object Files | Specifies whether to copy the compiled object files from the remote system to the local machine. |
+| Max Parallel Compilation Jobs | The number of process to create in parallel during compilation. The default is 1. If you are using Windows Subsystem for Linux (WSL) version 1, then the limit is 64 ttys. |
 
 ## Optimization
 
diff --git a/docs/linux/prop-pages/general-linux.md b/docs/linux/prop-pages/general-linux.md
@@ -1,7 +1,7 @@
 ---
 title: "General properties (Linux C++ Project)"
 description: "Describes the Linux project properties you can set in Visual Studio on the General properties page."
-ms.date: "01/14/2020"
+ms.date: "10/14/2020"
 ms.assetid: 56c800a9-3df9-4196-87b2-81adb00e4767
 ---
 # General properties (Linux C++)
@@ -27,6 +27,7 @@ Linux support is available in Visual Studio 2017 and later.
 | Remote Build Root Directory | Specifies a path to a directory on the remote machine or device. |
 | Remote Build Project Directory | Specifies a path to a directory on the remote machine or device for the project. |
 | Remote Deploy Directory | **Visual Studio 2019 version 16.1** Specifies the directory path on the remote machine or device to deploy the project. |
+| Enable Incremental Build | **Visual Studio 2019 version 16.?** Specifies whether to do incremental builds using Ninja. Builds will usually be faster for most projects with the setting enabled. | 
 | Remote Copy Include Directories | **Visual Studio 2019 version 16.5**  A list of directories to copy recursively from the Linux target. This property affects the remote header copy for IntelliSense, but not the build. It can be used when **IntelliSense Uses Compiler Defaults** is set to false. Use **Additional Include Directories** under the C/C++ General tab to specify additional include directories to use for both IntelliSense and build. |
 | Remote Copy Exclude Directories | **Visual Studio 2019 version 16.5** A list of directories *not* to copy from the Linux target. Usually, this property is used to remove subdirectories of the include directories. |
 | IntelliSense Uses Compiler Defaults | **Visual Studio 2019 version 16.5** Whether to query the compiler referenced by this project for its default list of include locations. These locations are automatically added to the list of remote directories to copy. Only set this property to false if the compiler doesn't support gcc-like parameters. Both gcc and clang compilers support queries for the include directories (for example, `g++ -x c++ -E -v -std=c++11`). |
