updates to porting guide

Author: mikeblome

docs/build/reference/std-specify-language-standard-version.md

@@ -28,7 +28,7 @@ The default **/std:c++14** option enables the set of C++14 features implemented
 
 - [u8 character literals](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4267.html)
 
-For additional information on which C++14 and C++17 features are enabled when **/std:c++14** is specified, see the notes in [Visual C++ Language Conformance](../../overview/visual-cpp-language-conformance.md).
+For additional information on which C++14 and C++17 features are enabled when **/std:c++14** is specified, see the notes in [Microsoft C++ language conformance table](../../overview/visual-cpp-language-conformance.md).
 
 The **/std:c++17** option enables the full set of C++17 features implemented by the MSVC compiler. This option disables compiler and standard library support for features that are changed or new in versions of the Working Draft and defect updates of the C++ Standard after C++17.
 
@@ -42,7 +42,7 @@ The **/std** option in effect during a C++ compilation can be detected by use of
 The **/std:c++14** and **/std:c++latest** options are available beginning in Visual Studio 2015 Update 3. The **/std:c++17** option is available beginning in Visual Studio 2017 version 15.3. As noted above, some C++17 standard behavior is enabled by the **/std:c++14** option, but all other C++17 features are enabled by **/std:c++17**. C++20 features are enabled by **/std:latest** until the implementation is complete.
 
 > [!NOTE]
-> Depending on the MSVC compiler version or update level, C++17 features may not be fully implemented or fully conformant when you specify the **/std:c++17** options. For an overview of C++ language conformance in Visual C++ by release version, see [Visual C++ Language Conformance](../../overview/visual-cpp-language-conformance.md).
+> Depending on the MSVC compiler version or update level, C++17 features may not be fully implemented or fully conformant when you specify the **/std:c++17** options. For an overview of C++ language conformance in Visual C++ by release version, see [Microsoft C++ language conformance table](../../overview/visual-cpp-language-conformance.md).
 
 ### To set this compiler option in the Visual Studio development environment
 

docs/cpp/welcome-back-to-cpp-modern-cpp.md

@@ -126,4 +126,4 @@ For more information, see the Stack Overflow article [Which C++ idioms are depre
 [C++ Language Reference](../cpp/cpp-language-reference.md)<br/>
 [Lambda Expressions](../cpp/lambda-expressions-in-cpp.md)<br/>
 [C++ Standard Library](../standard-library/cpp-standard-library-reference.md)<br/>
-[Visual C++ language conformance](../overview/visual-cpp-language-conformance.md)
+[Microsoft C++ language conformance table](../overview/visual-cpp-language-conformance.md)

docs/overview/cpp-conformance-improvements.md

@@ -804,7 +804,7 @@ struct Comparer  {
 
 ## <a name="improvements_150"></a> Conformance improvements in Visual Studio 2017 RTW (version 15.0)
 
-With support for generalized **constexpr** and non-static data member initialization (NSDMI) for aggregates, the Microsoft C++ compiler in Visual Studio 2017 is now complete for features added in the C++14 standard. However, the compiler still lacks a few features from the C++11 and C++98 standards. See [Visual C++ Language Conformance](../visual-cpp-language-conformance.md) for a table that shows the current state of the compiler.
+With support for generalized **constexpr** and non-static data member initialization (NSDMI) for aggregates, the Microsoft C++ compiler in Visual Studio 2017 is now complete for features added in the C++14 standard. However, the compiler still lacks a few features from the C++11 and C++98 standards. See [Microsoft C++ language conformance table](../visual-cpp-language-conformance.md) for a table that shows the current state of the compiler.
 
 ### C++11: Expression SFINAE support in more libraries
 
@@ -2844,4 +2844,4 @@ For the complete list of conformance improvements up through Visual Studio 2015
 
 ## See also
 
-[Visual C++ language conformance](../visual-cpp-language-conformance.md)
+[Microsoft C++ language conformance table](../visual-cpp-language-conformance.md)

docs/overview/visual-cpp-in-visual-studio.md

@@ -30,7 +30,7 @@ Find out what was new in C++ for each version of Visual Studio from 2003 through
 [C++ conformance improvements in Visual Studio](cpp-conformance-improvements.md)<br/>
 Learn about C++ conformance improvements in Visual Studio.
 
-[Visual C++ language conformance](visual-cpp-language-conformance.md)<br/>
+[Microsoft C++ language conformance table](visual-cpp-language-conformance.md)<br/>
 A list of conformance status by feature in the MSVC C++ compiler.
 
 [Visual C++ change history 2003 - 2015](../porting/visual-cpp-change-history-2003-2015.md)<br/>

docs/overview/what-s-new-for-visual-cpp-in-visual-studio.md

@@ -354,11 +354,11 @@ For a complete list of standard library improvements in Visual Studio 2017 RTM,
 - Added \<optional\>, \<variant\>, `shared_ptr::weak_type`, and \<cstdalign\>.
 - Enabled C++14 `constexpr` in `min(initializer_list)`, `max(initializer_list)`, and `minmax(initializer_list)`, and `min_element()`, `max_element()`, and `minmax_element()`.
 
-For more information, see [Visual C++ language conformance](../visual-cpp-language-conformance.md).
+For more information, see [Microsoft C++ language conformance table](../visual-cpp-language-conformance.md).
 
 ##### Visual Studio 2017 version 15.3
 
-- Several additional C++17 features have been implemented. For more information, see [Visual C++ Language Conformance](cpp-conformance-improvements.md#improvements_153).
+- Several additional C++17 features have been implemented. For more information, see [Microsoft C++ language conformance table](cpp-conformance-improvements.md#improvements_153).
 - Implemented P0602R0 "variant and optional should propagate copy/move triviality".
 - The standard library now officially tolerates dynamic RTTI being disabled via the [/GR-](../build/reference/gr-enable-run-time-type-information.md) option. Both `dynamic_pointer_cast()` and `rethrow_if_nested()` inherently require `dynamic_cast`, so the standard library now marks them as `=delete` under **/GR-**.
 - Even when dynamic RTTI has been disabled via **/GR-**, "static RTTI" in the form of `typeid(SomeType)` is still available, and powers several standard library components. The standard library now supports disabling this feature too, via **/D\_HAS\_STATIC\_RTTI=0**. This flag also disables `std::any`, the `target()` and `target_type()` member functions of `std::function`, and the `get_deleter()` friend member function of `std::shared_ptr` and `std::weak_ptr`.
@@ -416,7 +416,7 @@ For more information, see [Visual C++ language conformance](../visual-cpp-langua
 - `constexpr char_traits`
 - Deduction guides for the standard library
 
-For more information, see [Visual C++ language conformance](../visual-cpp-language-conformance.md).
+For more information, see [Microsoft C++ language conformance table](../visual-cpp-language-conformance.md).
 
 ### Performance and throughput fixes
 

docs/porting/introduction-to-visual-cpp-for-unix-users.md

@@ -1,58 +1,44 @@
 ---
-title: "Introduction to Visual C++ for UNIX Users"
-ms.date: "09/01/2017"
+title: "Introduction to Microsoft C++ for UNIX Users"
+ms.date: "10/23/2019"
 helpviewer_keywords: ["UNIX [C++]"]
 ms.assetid: 36108b31-e7fa-49a8-a1f7-7077fcbec873
 ---
-# Introduction to Visual C++ for UNIX Users
+# Introduction to Microsoft C++ for UNIX Users
 
-This topic provides information for UNIX users who are new to Visual Studio and want to become productive with C++ and the Visual Studio Integrated Development Environment (IDE).
+This topic provides information for users of all flavors of UNIX who are new to Visual Studio and want to become productive with C++ either from the command line or by using Visual Studio. You can use Visual Studio with the Microsoft C++ compiler to target Windows. You can also use the Visual Studio IDE with GCC or Clang in UNIX environments such as remote Linux machines, MinGW-w64, and Windows Subsystem for Linux. To use C++ in Visual Studio, the **Desktop Development with C++** workload must be installed. Open the Visual Studio Installer to install the workload or add or remove optional components. Also install the **Linux Development with C++** workload if you'll be targeting a remote Linux machine. For Android or iOS development, install the **Mobile Development with C++** workload.
 
-## Getting Started on the Command Line
+## Getting started on the command line
 
-You can use the C++ compiler from the command line in a similar way that you would use a UNIX command-line environment. You compile from the command prompt by using the command-line C and C++ compiler (CL.EXE), linker (LINK.EXE), and other tools, including NMAKE.EXE, the Microsoft version of the UNIX make utility.
+You can use the Microsoft C++ compiler from the command line in a similar way that you would use a UNIX command-line environment. You compile from the command prompt by using the command-line C and C++ compiler (CL.EXE), linker (LINK.EXE), and other tools, including NMAKE.EXE, the Microsoft version of the UNIX make utility.
 
-In UNIX, commands are installed in a common folder, such as /usr/bin. In Visual Studio, the command-line tools are installed in your Visual Studio installation directory in the VC\bin subdirectory and its subdirectories. Unlike UNIX, these tools are not available in a plain command prompt window. To use the command-line tools, use a developer command prompt shortcut, or run a developer command file such as vcvarsall.bat. This sets up the path and other environment variables that are necessary to compile C++ programs from the command line. For more information, see [Build C/C++ code on the command line](../build/building-on-the-command-line.md) and [Walkthrough: Compiling a Native C++ Program on the Command Line](../build/walkthrough-compiling-a-native-cpp-program-on-the-command-line.md).
+In UNIX, commands are installed in a common folder, such as /usr/bin. In Visual Studio, the command-line tools are installed in your Visual Studio installation directory in the VC\bin subdirectory and its subdirectories. Unlike UNIX, these tools are not available in a plain command prompt window. To use the command-line tools, you must use a special developer command prompt that sets up the path and other environment variables that are necessary to compile C++ programs. For more information, see [Build C/C++ code on the command line](../build/building-on-the-command-line.md) and [Walkthrough: Compiling a Native C++ Program on the Command Line](../build/walkthrough-compiling-a-native-cpp-program-on-the-command-line.md).
 
-To open a developer command prompt shortcut, enter *developer command prompt* in the desktop search control and choose the **Developer Command Prompt** result for your version of Visual Studio. To choose a developer command prompt that is preconfigured for a particular host and target architecture, open the **Start** menu (the Windows icon in the corner of the desktop) and then scroll to the folder for your version of Visual Studio, such as **Visual Studio 2017**. Open the folder and choose the command prompt shortcut for your preferred host and target architecture.
+## Debugging your code
 
-To take advantage of more powerful features, such as the Visual Studio debugger, IntelliSense code look-up and statement completion, visual designers, project management, and so on, you need to use the Visual Studio IDE.
+You can use the Visual Studio debugger for Microsoft C++ projects from the command line, or from within the IDE. Compile with the [/Z7, /Zi, /ZI (Debug Information Format)](../build/reference/z7-zi-zi-debug-information-format.md) switch to enable stepping through sources. For more information, see [Debugging Native Code](/visualstudio/debugger/debugging-native-code) and [Using the Visual Studio IDE for C++ Desktop Development](../ide/using-the-visual-studio-ide-for-cpp-desktop-development.md).
 
-## Debugging Your Code
+For programs compiled with GCC or Clang, Visual Studio invokes GDB, LLDB, or whatever custom debugger you specify.
 
-If you use the command line and run your applications on your development workstation, you will see that a dialog box to run the Visual Studio debugger is displayed when your code encounters a memory access violation, unhandled exception, or other unrecoverable errors. If you click **OK**, then the Visual Studio development environment is started, and the debugger will open to the point of failure. It is possible to debug your applications this way, and, in this case, your source code would only be available if you compiled with the [/Z7, /Zi, /ZI (Debug Information Format)](../build/reference/z7-zi-zi-debug-information-format.md) switch. For more information, see [Debugging Native Code](/visualstudio/debugger/debugging-native-code) and [Using the Visual Studio IDE for C++ Desktop Development](../ide/using-the-visual-studio-ide-for-cpp-desktop-development.md).
+## Visual Studio project system
 
-## Using the Development Environment
+The Visual Studio project system is called MSBuild. It uses project files in XML format; C++ project files have the extension .vcxproj. An application that consists of multiple libraries and executables, each potentially built with a different set of compiler options or even in a different language, are stored in multiple projects that are part of a single *solution*. A solution is an abstraction for a container to group multiple projects together. Information about solutions is stored in a solution file with the extension .sln. For more information, see [Solutions and Projects in Visual Studio](/visualstudio/ide/solutions-and-projects-in-visual-studio) and [Using the Visual Studio IDE for C++ Desktop Development](../ide/using-the-visual-studio-ide-for-cpp-desktop-development.md). From the main menu, choose **File** > **New** > **Project** to see the available Visual Studio project templates.
 
-It is easier to use the development environment to edit and build your source code in a *project*. A project is a collection of source and related files that will be compiled into a single unit, such as a library or executable. A project also contains information on how the files are to be built. Information about projects is stored in a project file with the extension .prj.
+Starting in Visual Studio 2017, support for CMake projects is added, as well as options for using the Microsoft C++ compiler with any arbitrary build system, or with a loose folder of source files and no project files. For more information, see [CMake projects in Visual Studio](../build/cmake-projects-in-visual-studio.md) and [Open Folder projects in Visual Studio](../build/open-folder-projects.md).
 
-An application that consists of multiple libraries and executables, each potentially built with a different set of compiler options or even in a different language, are stored in multiple projects that are part of a single *solution*. A solution is an abstraction for a container to group multiple projects together. Information about solutions is stored in a solution file with the extension .sln. For more information, see [Solutions and Projects in Visual Studio](/visualstudio/ide/solutions-and-projects-in-visual-studio) and [Using the Visual Studio IDE for C++ Desktop Development](../ide/using-the-visual-studio-ide-for-cpp-desktop-development.md).
-
-## Importing Your Existing Code
-
-You can use the C++ compiler to build existing code that is set up to compile with or without a makefile and put it into a Visual Studio project. For more information, see [How to: Create a C++ Project from Existing Code](../build/how-to-create-a-cpp-project-from-existing-code.md).
-
-## Creating a New Project
-
-You can create new projects in the development environment. Visual Studio provides numerous templates that provide standard code for various common projects. You can use application wizards to generate projects with code outlines for various application types.
-
-You can start with an empty project by using the **Console Application (Win32) Wizard**. Select the **Empty Project** check box. You can then add new and existing files to the project later.
-
-When you create a project, you must name the project. By default, the project name equals the name of the dynamic-link library (DLL) or executable that is build from the project. For more information, see [Creating Solutions and Projects](/visualstudio/ide/creating-solutions-and-projects).
-
-## Microsoft-Specific Modifiers
+## Microsoft-specific modifiers
 
 The Microsoft C++ compiler implements several extensions to the standard C++ programming language to support programming for Windows operating systems. These extensions are used to specify storage class attributes, function calling conventions, and based addressing, among other things. For a complete list of all supported C++ extensions, see [Microsoft-Specific Modifiers](../cpp/microsoft-specific-modifiers.md).
 
-You can disable all Microsoft-specific extensions to C++ by using the `/Za` compiler option. This option is recommended if you want to write code to run on multiple platforms. For more information on the `/Za` compiler option, see [/Za, /Ze (Disable Language Extensions)](../build/reference/za-ze-disable-language-extensions.md). For more information on C++ compiler conformance, see [Visual C++ Language Conformance](../overview/visual-cpp-language-conformance.md) and [Nonstandard Behavior](../cpp/nonstandard-behavior.md).
+You can disable all Microsoft-specific extensions to C++ by using the `/Za` compiler option. This option is recommended if you want to write code to run on multiple platforms. For more information on the `/Za` compiler option, see [/Za, /Ze (Disable Language Extensions)](../build/reference/za-ze-disable-language-extensions.md). For more information on C++ compiler conformance, see [Microsoft C++ language conformance table](../overview/visual-cpp-language-conformance.md) and [Nonstandard Behavior](../cpp/nonstandard-behavior.md).
 
-## Precompiled Headers
+## Precompiled headers
 
 The Microsoft C and C++ compilers provide options for precompiling any C or C++ code, including inline code. Using this performance feature, you can compile a stable body of code, store the compiled state of the code in a file, and, during subsequent compilations, combine the precompiled code with code that is still under development. Each subsequent compilation is faster because the stable code does not need to be recompiled.
 
-By default, all precompiled code is specified in the files *pch.h* and *pch.cpp* (*stdafx.h* and *stdafx.cpp* in Visual Studio 2017 and earlier). The **New Project** wizard will automatically create these files for you unless you deselect the **Precompiled header** option. For more information on precompiled headers, see [Creating Precompiled Header Files](../build/creating-precompiled-header-files.md).
+By default, all precompiled code is specified in the files *pch.h* and *pch.cpp* (*stdafx.h* and *stdafx.cpp* in Visual Studio 2017 and earlier). For more information on precompiled headers, see [Creating Precompiled Header Files](../build/creating-precompiled-header-files.md).
 
-## Related Sections
+## Related sections
 
 For more information, see [Porting from UNIX to Win32](../porting/porting-from-unix-to-win32.md).