Merge pull request MicrosoftDocs#3330 from corob-msft/docs/corob/issue-fixes-2020-12-08

Address cpp-docs 2634

Author: PMEds28

docs/dotnet/dotnet-programming-with-cpp-cli-visual-cpp.md

@@ -1,53 +1,72 @@
 ---
-title: ".NET Programming with C++/CLI (Visual C++)"
-ms.date: "09/18/2018"
+title: ".NET programming with C++/CLI"
+description: "Learn how to use C++/CLI to create .NET apps and components in Visual Studio."
+ms.date: 12/08/2020
 helpviewer_keywords: ["programming [C++], .NET programming", ".NET Framework [C++]", ".NET applications [C++]", "Visual C++, .NET programming"]
-ms.assetid: 2c7f3b0f-a266-4f0e-b318-d6f1371e04a9
 ---
-# .NET Programming with C++/CLI (Visual C++)
+# .NET programming with C++/CLI
 
-**Visual Studio 2015**: By default, CLR projects created with Visual Studio 2015 target .NET Framework 4.5.2. To target .NET Framework 4.6 when you create a new project, in the **New Project** dialog, change the target framework in the dropdown at the top middle of the dialog. To change the target framework for an existing project, close the project, edit the project file (.vcxproj), and change the value of the Target Framework Version to 4.6. Next time you open the project, the settings will take effect.
+::: moniker range="msvc-140"
 
-**Visual Studio 2017**: In Visual Studio 2017, the default framework is 4.6.1 and the Framework version selector is at the bottom of the **New Project Dialog**. C++/CLI itself is not installed by default. To install the component, open the Visual Studio Installer and choose the C++/CLI component under Visual C++.
+By default, CLR projects created with Visual Studio 2015 target .NET Framework 4.5.2. You can target .NET Framework 4.6 when you create a new project. In the **New Project** dialog, change the target framework in the dropdown at the top middle of the dialog. To change the target framework for an existing project, close the project, edit the project file (*`.vcxproj`*), and change the value of the Target Framework Version to 4.6. The changes take effect the next time you open the project.
 
-## In This Section
+::: moniker-end
+::: moniker range="msvc-150"
 
-[C++/CLI Tasks](../dotnet/cpp-cli-tasks.md)
+In Visual Studio 2017, the default target .NET Framework is 4.6.1. The Framework version selector is at the bottom of the **New Project** dialog.
 
-[Native and .NET Interoperability](../dotnet/native-and-dotnet-interoperability.md)
+## Install C++/CLI support in Visual Studio 2017
 
-[Pure and Verifiable Code (C++/CLI)](../dotnet/pure-and-verifiable-code-cpp-cli.md)
+C++/CLI itself isn't installed by default when you install a Visual Studio C++ workload. To install the component after Visual Studio is installed, open the Visual Studio Installer. Choose the **Modify** button next to your installed version of Visual Studio. Select the **Installed components** tab. Scroll down to the **Compilers, build tools, and runtimes** section, and select **C++/CLI support**. Choose **Modify** to update Visual Studio.
 
-[Regular Expressions (C++/CLI)](../dotnet/regular-expressions-cpp-cli.md)
+::: moniker-end
+::: moniker range="msvc-160"
 
-[File Handling and I/O (C++/CLI)](../dotnet/file-handling-and-i-o-cpp-cli.md)
+In Visual Studio 2019, the default target framework for .NET Core projects is 5.0. For .NET Frameworks projects, the default is 4.7.2. The .NET Framework version selector is on the **Configure your new project** page of the **Create a new project** dialog.
+## Install C++/CLI support in Visual Studio 2019
 
-[Graphics Operations (C++/CLI)](../dotnet/graphics-operations-cpp-cli.md)
+C++/CLI itself isn't installed by default when you install a Visual Studio C++ workload. To install the component after Visual Studio is installed, open the Visual Studio Installer. Choose the **Modify** button next to your installed version of Visual Studio. Select the **Installed components** tab. Scroll down to the **Compilers, build tools, and runtimes** section, and select the latest **C++/CLI support for v142 build tools** component. Choose **Modify** to update Visual Studio.
 
-[Windows Operations (C++/CLI)](../dotnet/windows-operations-cpp-cli.md)
+::: moniker-end
 
-[Data Access Using ADO.NET (C++/CLI)](../dotnet/data-access-using-adonet-cpp-cli.md)
+## In this section
 
-[Interoperability with Other .NET Languages (C++/CLI)](../dotnet/interoperability-with-other-dotnet-languages-cpp-cli.md)
+[C++/CLI tasks](../dotnet/cpp-cli-tasks.md)
+
+[Native and .NET interoperability](../dotnet/native-and-dotnet-interoperability.md)
+
+[Pure and verifiable code (C++/CLI)](../dotnet/pure-and-verifiable-code-cpp-cli.md)
+
+[Regular expressions (C++/CLI)](../dotnet/regular-expressions-cpp-cli.md)
+
+[File handling and I/O (C++/CLI)](../dotnet/file-handling-and-i-o-cpp-cli.md)
+
+[Graphics operations (C++/CLI)](../dotnet/graphics-operations-cpp-cli.md)
+
+[Windows operations (C++/CLI)](../dotnet/windows-operations-cpp-cli.md)
+
+[Data access using ADO.NET (C++/CLI)](../dotnet/data-access-using-adonet-cpp-cli.md)
+
+[Interoperability with other .NET languages (C++/CLI)](../dotnet/interoperability-with-other-dotnet-languages-cpp-cli.md)
 
 [Serialization (C++/CLI)](../dotnet/serialization-cpp-cli.md)
 
-[Managed Types (C++/CLI)](../dotnet/managed-types-cpp-cli.md)
+[Managed types (C++/CLI)](../dotnet/managed-types-cpp-cli.md)
 
 [Reflection (C++/CLI)](../dotnet/reflection-cpp-cli.md)
 
-[Strong Name Assemblies (Assembly Signing) (C++/CLI)](../dotnet/strong-name-assemblies-assembly-signing-cpp-cli.md)
+[Strong Name assemblies (assembly signing) (C++/CLI)](../dotnet/strong-name-assemblies-assembly-signing-cpp-cli.md)
 
-[Debug Class (C++/CLI)](../dotnet/debug-class-cpp-cli.md)
+[Debug class (C++/CLI)](../dotnet/debug-class-cpp-cli.md)
 
-[STL/CLR Library Reference](../dotnet/stl-clr-library-reference.md)
+[STL/CLR library reference](../dotnet/stl-clr-library-reference.md)
 
-[C++ Support Library](../dotnet/cpp-support-library.md)
+[C++ support library](../dotnet/cpp-support-library.md)
 
 [Exceptions in C++/CLI](../dotnet/exceptions-in-cpp-cli.md)
 
 [Boxing (C++/CLI)](../dotnet/boxing-cpp-cli.md)
 
 ## See also
 
-[Native and .NET Interoperability](../dotnet/native-and-dotnet-interoperability.md)
+[Native and .NET interoperability](../dotnet/native-and-dotnet-interoperability.md)

docs/dotnet/how-to-create-clr-console-applications-cpp-cli.md

@@ -1,57 +1,140 @@
 ---
 title: "How to: Create CLR Console Applications (C++/CLI)"
-ms.date: "11/04/2016"
+description: "Learn how to create CLR Console App projects to use C++/CLI in Visual Studio."
+ms.date: 12/08/2020
 helpviewer_keywords: ["console applications, templates", "CLR console applications, project template"]
-ms.assetid: e89bce3c-706f-4ae0-8a90-cb1a0f674e70
 ---
 # How to: Create CLR Console Applications (C++/CLI)
 
-You can use the Console Application template to create a console app project that already has essential project references and files.
+::: moniker range="msvc-140"
 
-Typically, a console app is compiled into a stand-alone executable file but doesn't have a graphical user interface. A user runs the console app at a command prompt and uses the command prompt to issue instructions to the running app. Also at the command prompt, the app provides output information. The immediacy of a console app makes it a great way to learn programming techniques without concern for implementing a user interface.
+You can use the  **CLR Console Application** template in the **New Project** dialog to create a console app project that already has essential project references and files.
 
-When you use the Console Application template to create a project, it automatically adds these references and files:
+::: moniker-end
+::: moniker range="msvc-150"
+
+You can use the **CLR Console App** template in the **New Project** dialog to create a console app project that already has essential project references and files.
+
+C++/CLI support isn't installed by default when you install a Visual Studio C++ workload. If you don't see a CLR heading under Visual C++ in the **New Project** dialog, you may need to install C++/CLI support. For more information, see [.NET programming with C++/CLI](../dotnet/dotnet-programming-with-cpp-cli-visual-cpp.md).
+
+::: moniker-end
+::: moniker range="msvc-160"
+
+You can use the **CLR Console App (.NET Framework)** template in the **Create a new project** dialog to create a console app project that already has essential project references and files.
+
+C++/CLI support isn't installed by default when you install a Visual Studio C++ workload. If you don't see CLR project templates in the  **Create a new project** dialog, you may need to install C++/CLI support. For more information, see [.NET programming with C++/CLI](../dotnet/dotnet-programming-with-cpp-cli-visual-cpp.md).
+
+::: moniker-end
+
+Typically, a console app is compiled into a stand-alone executable file but doesn't have a graphical user interface. Users run the console app at a command prompt. They can use the command line to issue instructions to the running app. The app provides output information as text in the command window. The immediate feedback of a console app makes it a great way to learn programming. You don't need to worry about how to implement a graphical user interface.
+
+::: moniker range="msvc-140"
+
+When you use the CLR Console Application template to create a project, it automatically adds these references and files:
 
 - References to these .NET Framework namespaces:
 
-  - <xref:System.AppDomainManager>—Contains fundamental classes and base classes that define commonly used values and reference data types, events and event handlers, interfaces, attributes, and processing exceptions.
+  - <xref:System>, <xref:System.Data>, <xref:System.Xml>: These references contain the fundamental classes that define commonly used types, events, interfaces, attributes, and exceptions.
 
-  - mscorlib—The assembly DLL that supports .NET Framework development.
+  - *`mscorlib.dll`*: The assembly DLL that supports .NET Framework development.
 
 - Source files:
 
-  - Console (.cpp file)—The main source file and entry point into the app that you just created. It identifies the project .dll file and the project namespace. Provide your own code in this file.
+  - *`ConsoleApplicationName.cpp`*: The main source file and entry point into the app. This file has the base name you specified for your project. It identifies the project DLL file and the project namespace. Provide your own code in this file.
 
-  - AssemblyInfo.cpp—Contains attributes, files, resources, types, versioning information, signing information, and so on that you can use to modify the project's assembly metadata. For more information, see [Assembly Contents](/dotnet/framework/app-domains/assembly-contents).
+  - *`AssemblyInfo.cpp`*: Contains attributes and settings that you can use to modify the project's assembly metadata. For more information, see [Assembly contents](/dotnet/framework/app-domains/assembly-contents).
 
-  - Stdafx.cpp—Used to build a precompiled header file that's named Win32.pch and a precompiled types file that's named StdAfx.obj.
+  - *`stdafx.cpp`*: Used to build a precompiled header file that's named *`ConsoleApplicationName.pch`* and a precompiled types file that's named *`stdafx.obj`*.
 
 - Header files:
 
-  - Stdafx.h—Used to build a precompiled header file that's named Win32.pch and a precompiled types file that's named StdAfx.obj.
+  - *`stdafx.h`*: Used to build a precompiled header file that's named *`ConsoleApplicationName.pch`* and a precompiled types file that's named *`stdafx.obj`*.
 
-  - resource.h—A generated include file for app.rc.
+  - *`resource.h`*: A generated include file for *`app.rc`*.
 
 - Resource files:
 
-  - app.rc—The resource script file of a program.
+  - *`app.rc`*: The resource script file of a program.
 
-  - app.ico—The icon file of a program.
+  - *`app.ico`*: The icon file of a program.
 
-- ReadMe.txt—Describes the files in the project.
+- *`ReadMe.txt`*: Describes the files in the project.
 
-## To create a common language runtime (CLR) console app project
+::: moniker-end
+::: moniker range=">=msvc-150"
+
+When you use the CLR Console App template to create a project, it automatically adds these references and files:
+
+- References to these .NET Framework namespaces:
 
-1. On the menu bar, choose **File**, **New**, **Project**.
+  - <xref:System>, <xref:System.Data>, <xref:System.Xml>: These references contain the fundamental classes that define commonly used types, events, interfaces, attributes, and exceptions.
 
-1. In the **New Project** dialog box, under **Installed Templates**, select the **Visual C++** node, select the **CLR** node, and then select the Console Application template.
+  - *`mscorlib.dll`*: The assembly DLL that supports .NET Framework development.
+
+- Source files:
+
+  - *`ConsoleApplicationName.cpp`*: The main source file and entry point into the app. This file has the base name you specified for your project. It identifies the project DLL file and the project namespace. Provide your own code in this file.
+
+  - *`AssemblyInfo.cpp`*: Contains attributes and settings that you can use to modify the project's assembly metadata. For more information, see [Assembly contents](/dotnet/framework/app-domains/assembly-contents).
+
+  - *`pch.cpp`*: Used to build a precompiled header file that's named *`ConsoleApplicationName.pch`* and a precompiled types file that's named *`pch.obj`*.
+
+- Header files:
+
+  - *`pch.h`*: Used to build a precompiled header file that's named *`ConsoleApplicationName.pch`* and a precompiled types file that's named *`pch.obj`*.
+
+  - *`Resource.h`*: A generated include file for *`app.rc`*.
+
+- Resource files:
+
+  - *`app.rc`*: The resource script file of a program.
+
+  - *`app.ico`*: The icon file of a program.
+
+::: moniker-end
+
+## To create a CLR console app project
+
+::: moniker range="msvc-140"
+
+1. On the menu bar, choose **File** > **New** > **Project**.
+
+1. In the **New Project** dialog box, select the **Installed** > **Templates** > **Visual C++** > **CLR** node, and then select the **CLR Console Application** template.
+
+1. In the **Name** box, enter a unique name for your application.
+
+   You can specify other project and solution settings, but they're not required.
+
+1. Choose the **OK** button to generate the project and source files.
+
+::: moniker-end
+::: moniker range="msvc-150"
+
+1. On the menu bar, choose **File** > **New** > **Project**.
+
+1. In the **New Project** dialog box, select the **Installed** > **Visual C++** > **CLR** node, and then select the **CLR Console App** template.
 
 1. In the **Name** box, enter a unique name for your application.
 
-   You can specify other project and solution settings, but they are not required.
+   You can specify other project and solution settings, but they're not required.
+
+1. Choose the **OK** button to generate the project and source files.
+
+::: moniker-end
+::: moniker range="msvc-160"
+
+1. On the menu bar, choose **File** > **New** > **Project**.
+
+1. In the **Create a new project** dialog box, enter "clr console" in the search box. Select the **CLR Console App (.NET Framework)** template, and then choose **Next**.
+
+1. In the **Name** box, enter a unique name for your application.
+
+   You can specify other project and solution settings, but they're not required.
+
+1. Choose the **Create** button to generate the project and source files.
 
-1. Choose the **OK** button.
+::: moniker-end
 
 ## See also
 
-[CLR Projects](../build/reference/files-created-for-clr-projects.md)
+[CLR projects](../build/reference/files-created-for-clr-projects.md)