Update publish tutorial

docs/core/tutorials/publishing-with-visual-studio.md

@@ -1,49 +1,69 @@
 ---
-title: Publish your .NET Core Hello World application with Visual Studio 2017
+title: Publish your .NET Core Hello World application with Visual Studio
 description: Publishing creates the set of files that are needed to run your .NET Core application.
 author: BillWagner
 ms.author: wiwagn
-ms.date: 10/05/2017
+ms.date: 12/10/2019
 ms.custom: "vs-dotnet, seodec18"
 ---
-# Publish your .NET Core Hello World application with Visual Studio 2017
+# Publish your .NET Core Hello World application with Visual Studio 2019
 
-In [Build a Hello World application with .NET Core in Visual Studio](with-visual-studio.md), you built a Hello World console application. In [Debug your Hello World application with Visual Studio](debugging-with-visual-studio.md), you tested it using the Visual Studio debugger. Now that you're sure that it works as expected, you can publish it so that other users can run it. Publishing creates the set of files that are needed to run your application, and you can deploy the files by copying them to a target machine.
+In [Create a Hello World application with .NET Core in Visual Studio](with-visual-studio.md), you built a Hello World console application. In [Debug your Hello World application with Visual Studio](debugging-with-visual-studio.md), you tested it using the Visual Studio debugger. Now that you're sure that it works as expected, you can publish it so that other users can run it. Publishing creates the set of files that are needed to run your application. To deploy the files, copy them to the target machine.
 
-To publish and run your application:
+## Publish the app
 
 1. Make sure that Visual Studio is building the Release version of your application. If necessary, change the build configuration setting on the toolbar from **Debug** to **Release**.
 
    ![Visual Studio toolbar with release build selected](media/publishing-with-visual-studio/visual-studio-toolbar-release.png)
 
-1. Right-click on the **HelloWorld** project (not the HelloWorld solution) and select **Publish** from the menu. You can also select **Publish HelloWorld** from the main Visual Studio **Build** menu.
+1. Right-click on the **HelloWorld** project (not the HelloWorld solution) and select **Publish** from the menu. (You can also select **Publish HelloWorld** from the main **Build** menu.)
 
    ![Visual Studio Publish context menu](media/publishing-with-visual-studio/publish-context-menu.png)
+
+1. On the **Pick a publish target** page, select **Folder**, and then select **Create Profile**.
 
-   ![Visual Studio Publish window](media/publishing-with-visual-studio/publish-settings-window.png)
+   ![Pick a publish target in Visual Studio](media/publishing-with-visual-studio/pick-publish-target.png)
+
+1. On the **Publish** page, select **Publish**.
 
-1. Open a console window. For example in the **Type here to search** text box in the Windows taskbar, enter `Command Prompt` (or `cmd` for short), and open a console window by either selecting the **Command Prompt** desktop app or pressing Enter if it's selected in the search results.
+   ![Visual Studio Publish window](media/publishing-with-visual-studio/publish-page.png)
+
+## Inspect the files
 
-1. Navigate to the published application in the `bin\release\PublishOutput` subdirectory of your application's project directory. As the following figure shows, the published output includes the following four files:
+The publishing process creates a framework-dependent deployment, which is a type of deployment where the published application runs on any platform supported by .NET Core with .NET Core installed on the system. Users can run the published app by double-clicking the executable or issuing the `dotnet HelloWorld.dll` command from a command prompt.
+
+In the following steps, you'll look at the files created by the publish process.
+
+1. Open a command prompt.
+
+   One way to open a command prompt is to enter **Command Prompt** (or **cmd** for short) in the search box on the Windows taskbar. Select the **Command Prompt** desktop app, or press **Enter** if it's already selected in the search results.
+
+1. Navigate to the published application in the *bin\Release\netcoreapp3.1\publish* subdirectory of the application's project directory.
+
+   ![Console window showing published files](media/publishing-with-visual-studio/published-files-output.png)
+
+   As the image shows, the published output includes the following files:
 
       * *HelloWorld.deps.json*
 
-         The application's runtime dependencies file. It defines the .NET Core components and the libraries (including the dynamic link library that contains your application) needed to run your application. For more information, see [Runtime Configuration Files](https://github.com/dotnet/cli/blob/85ca206d84633d658d7363894c4ea9d59e515c1a/Documentation/specs/runtime-configuration-file.md).
+         This is the application's runtime dependencies file. It defines the .NET Core components and the libraries (including the dynamic link library that contains your application) needed to run the app. For more information, see [Runtime configuration files](https://github.com/dotnet/cli/blob/85ca206d84633d658d7363894c4ea9d59e515c1a/Documentation/specs/runtime-configuration-file.md).
 
       * *HelloWorld.dll*
 
-         The file that contains your application. It is a dynamic link library that can be executed by entering the `dotnet HelloWorld.dll` command in a console window.
+         This is the [framework-dependent deployment](../deploying/deploy-with-cli.md#framework-dependent-deployment) version of the application. To execute this dynamic link library, enter `dotnet HelloWorld.dll` at a command prompt.
+
+      * *HelloWorld.exe*
+
+         This is the [framework-dependent executable](../deploying/deploy-with-cli.md#framework-dependent-executable) version of the application. To run it, enter `HelloWorld.exe` at a command prompt.
 
       * *HelloWorld.pdb* (optional for deployment)
 
-         A file that contains debug symbols. You aren't required to deploy this file along with your application, although you should save it in the event that you need to debug the published version of your application.
+         This is the debug symbols file. You aren't required to deploy this file along with your application, although you should save it in the event that you need to debug the published version of your application.
 
       * *HelloWorld.runtimeconfig.json*
 
-         The application's runtime configuration file. It identifies the version of .NET Core that your application was built to run on. For more information, see [Runtime Configuration Files](https://github.com/dotnet/cli/blob/85ca206d84633d658d7363894c4ea9d59e515c1a/Documentation/specs/runtime-configuration-file.md).
-
-   ![Console window showing published files](media/publishing-with-visual-studio/published-files-output.png)
+         This is the application's runtime configuration file. It identifies the version of .NET Core that your application was built to run on. For more information, see [Runtime configuration files](https://github.com/dotnet/cli/blob/85ca206d84633d658d7363894c4ea9d59e515c1a/Documentation/specs/runtime-configuration-file.md).
 
-The publishing process creates a framework-dependent deployment, which is a type of deployment where the published application will run on any platform supported by .NET Core with .NET Core installed on the system. Users can run your application by issuing the `dotnet HelloWorld.dll` command from a console window.
+## Additional resources
 
-For more information on publishing and deploying .NET Core applications, see [.NET Core Application Deployment](../deploying/index.md).
+- [.NET Core application deployment](../deploying/index.md)