Merge pull request #4345 from MicrosoftDocs/master

Merge to live for VS 2019 release

Author: gewarren

.openpublishing.redirection.json

@@ -2205,6 +2205,11 @@
             "redirect_url": "/visualstudio/port-migrate-and-upgrade-visual-studio-projects",
             "redirect_document_id": false
         },
+        { 
+            "source_path": "docs/porting/port-migrate-upgrade-visual-studio-projects-2019.md", 
+            "redirect_url": "/visualstudio/porting/port-migrate-and-upgrade-visual-studio-projects", 
+            "redirect_document_id": false 
+        },
         {
             "source_path": "docs/profiling/analyze-cpu-usage-in-a-windows-universal-app.md",
             "redirect_url": "/visualstudio/profiling/beginners-guide-to-performance-profiling",

docs/azure/vs-azure-tools-publishing-using-powershell-scripts.md

@@ -18,7 +18,7 @@ Using these scripts, you can provision customized versions (also known as dev an
 
 ## Prerequisites
 
-* Visual Studio 2015 or later with the **Azure workload** installed, or Visual Studio 2013 and Azure SDK 2.3 or later. See [Visual Studio Downloads](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019+rc). (You don't need the Azure SDK to generate the scripts for web projects. This feature is for web projects, not web roles in cloud services.)
+* Visual Studio 2015 or later with the **Azure workload** installed, or Visual Studio 2013 and Azure SDK 2.3 or later. See [Visual Studio Downloads](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019). (You don't need the Azure SDK to generate the scripts for web projects. This feature is for web projects, not web roles in cloud services.)
 * Azure PowerShell 0.7.4 or later. See [How to install and configure Azure PowerShell](/powershell/azure/overview).
 * [Windows PowerShell 3.0](http://go.microsoft.com/?linkid=9811175) or later.
 

docs/azure/vs-azure-tools-resources-managing-with-cloud-explorer.md

@@ -18,7 +18,7 @@ Like the [Azure portal](http://go.microsoft.com/fwlink/p/?LinkID=525040), Cloud
 
 ## Prerequisites
 
-* Visual Studio 2017 or later (see [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019+rc)) with the **Azure workload** selected. You can also use an earlier version of Visual Studio with the [Microsoft Azure SDK for .NET 2.9](https://www.microsoft.com/download/details.aspx?id=51657).
+* Visual Studio 2017 or later (see [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019)) with the **Azure workload** selected. You can also use an earlier version of Visual Studio with the [Microsoft Azure SDK for .NET 2.9](https://www.microsoft.com/download/details.aspx?id=51657).
 * Microsoft Azure account - If you don't have an account, you can [sign up for a free trial](http://go.microsoft.com/fwlink/?LinkId=623901) or [activate your Visual Studio subscriber benefits](http://go.microsoft.com/fwlink/?LinkId=623901).
 
 > [!NOTE]

docs/containers/docker-deploy-app-service.md

@@ -23,7 +23,7 @@ To complete this tutorial:
 - Install the latest version of [Visual Studio 2017](https://azure.microsoft.com/downloads/) with the "ASP.NET and web development" workload
 ::: moniker-end
 ::: moniker range=">=vs-2019"
-- [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019+rc) with the *ASP.NET and web development* workload.
+- [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019) with the *ASP.NET and web development* workload.
 ::: moniker-end
 - Install [Docker Desktop](https://docs.docker.com/docker-for-windows/install/)
 

docs/containers/includes/vs-2019/docker-tools.md

@@ -14,7 +14,7 @@ With Visual Studio, you can easily build, debug, and run containerized ASP.NET C
 ## Prerequisites
 
 * [Docker Desktop](https://hub.docker.com/editions/community/docker-ce-desktop-windows)
-* [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019+rc) with the **Web Development**, **Azure Tools** workload, and/or **.NET Core cross-platform development** workload installed
+* [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019) with the **Web Development**, **Azure Tools** workload, and/or **.NET Core cross-platform development** workload installed
 * [.NET Core 2.2 Development Tools](https://dotnet.microsoft.com/download/dotnet-core/2.2) for development with .NET Core 2.2
 * To publish to Azure Container Registry, an Azure subscription. [Sign up for a free trial](https://azure.microsoft.com/en-us/offers/ms-azr-0044p/).
 

docs/containers/tutorial-kubernetes-tools.md

@@ -24,7 +24,7 @@ To leverage this new functionality, you'll need:
 - The [Kubernetes tools for Visual Studio](https://aka.ms/get-vsk8stools), available as a separate download.
 ::: moniker-end
 ::: moniker range="vs-2019"
-- [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019+rc) with the *ASP.NET and web development* workload.
+- [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019) with the *ASP.NET and web development* workload.
 ::: moniker-end
 - [Docker Desktop](https://store.docker.com/editions/community/docker-ce-desktop-windows) installed on your development workstation (that is, where you run Visual Studio), if you wish to build Docker images, debug Docker containers running locally, or publish to AKS. (Docker is *not* required for building and debugging Docker containers in AKS using Azure Dev Spaces.)
 ::: moniker range="vs-2017"

docs/containers/tutorial-multicontainer.md

@@ -22,7 +22,7 @@ In this tutorial, you'll learn how to manage more than one container and communi
 
 ::: moniker range=">= vs-2019"
 * [Docker Desktop](https://hub.docker.com/editions/community/docker-ce-desktop-windows)
-* [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019+rc) with the **Web Development**, **Azure Tools** workload, and/or **.NET Core cross-platform development** workload installed
+* [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019) with the **Web Development**, **Azure Tools** workload, and/or **.NET Core cross-platform development** workload installed
 * [.NET Core 2.2 Development Tools](https://dotnet.microsoft.com/download/dotnet-core/2.2) for development with .NET Core 2.2
 ::: moniker-end
 

docs/containers/vs-azure-tools-docker-edit-and-refresh.md

@@ -32,7 +32,7 @@ The following tools must be installed.
 
 ::: moniker range="vs-2019"
 
-* [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019+rc) with the Web Development workload installed.
+* [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019) with the Web Development workload installed.
 
 ::: moniker-end
 

docs/containers/vs-azure-tools-docker-hosting-web-apps-in-docker.md

@@ -27,7 +27,7 @@ To complete this tutorial:
 * Install the latest version of [Visual Studio 2017](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2017)with the "ASP.NET and web development" workload
 ::: moniker-end
 ::: moniker range=">=vs-2019"
-* Install the latest version of [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019+rc) with the "ASP.NET and web development" workload
+* Install the latest version of [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019) with the "ASP.NET and web development" workload
 ::: moniker-end
 * Install [Docker for Windows](https://docs.docker.com/docker-for-windows/install/)
 

docs/debugger/debug-live-azure-applications.md

@@ -44,40 +44,29 @@ In this tutorial, you will:
 
     > [!IMPORTANT]
     > To snapshot debug, you need to open the *same version of source code* that is published to your Azure App Service.
-::: moniker range="vs-2019"
+::: moniker range="<=vs-2017"
 
 2. In the Cloud Explorer (**View > Cloud Explorer**), right-click the Azure App Service your project is deployed to and select **Attach Snapshot Debugger**.
 
    ![Launch the snapshot debugger](../debugger/media/snapshot-launch.png)
 
-    The first time you select **Attach Snapshot Debugger**, you're prompted to install the Snapshot Debugger site extension on your Azure App Service. This installation requires a restart of your Azure App Service.
-
 ::: moniker-end
-::: moniker range=">= vs-2019"
-2. Attach the Snapshot Debugger. You can use one of several different methods:
-
-    * Choose **Debug > Attach Snapshot Debugger...**. Select the Azure App Service your project is deployed to and an Azure storage account, and then click **Attach**.
+::: moniker range=">=vs-2019"
+2. Choose **Debug > Attach Snapshot Debugger...**. Select the Azure App Service your project is deployed to and an Azure storage account, and then click **Attach**.
 
       ![Launch the snapshot debugger from the Debug menu](../debugger/media/snapshot-debug-menu-attach.png)
 
-    * Right click on your project and select **Publish**, and then on the Publish page click **Attach Snapshot Debugger**. Select the Azure App Service your project is deployed to and an Azure storage account, and then click **Attach**.
-    ![Launch the snapshot debugger from the Publish page](../debugger/media/snapshot-publish-attach.png)
-
-    * In the Debug target drop-down menu select **Snapshot Debugger**, hit **F5** and if necessary select the Azure App Service your project is deployed to and an Azure storage account, and then click **Attach**.
-    ![Launch the snapshot debugger from the F5 drop-down menu](../debugger/media/snapshot-F5-dropdown-attach.png)
-
-    * Using the Cloud Explorer (**View > Cloud Explorer**), right-click the Azure App Service your project is deployed to and select an Azure storage account, and then click **Attach Snapshot Debugger**.
+      ![Select Azure Resource](../debugger/media/snapshot-select-azure-resource-appservices.png)
 
-      ![Launch the snapshot debugger from the Cloud Explorer](../debugger/media/snapshot-launch.png)
-
-    The first time you select **Attach Snapshot Debugger**, you're prompted to install the Snapshot Debugger site extension on your Azure App Service. This installation requires a restart of your Azure App Service.
 ::: moniker-end
 
-   Visual Studio is now in snapshot debugging mode.
+  > [!IMPORTANT]
+  > The first time you select **Attach Snapshot Debugger**, you're prompted to install the Snapshot Debugger site extension on your Azure App Service. This installation requires a restart of your Azure App Service.
 
   > [!NOTE]
   > The Application Insights site extension also supports Snapshot Debugging. If you encounter a "site extension out of date" error message, see [troubleshooting tips and known issues for snapshot debugging](../debugger/debug-live-azure-apps-troubleshooting.md) for upgrading details.
 
+   Visual Studio is now in snapshot debugging mode.
    ![Snapshot debugging mode](../debugger/media/snapshot-message.png)
 
    The **Modules** window shows you when all the modules have loaded for the Azure App Service (choose **Debug > Windows > Modules** to open this window).
@@ -151,7 +140,7 @@ In addition to taking a snapshot when a snappoint is hit, you can also configure
 
     If you choose **Send to Output Window**, when the logpoint is hit, the message appears in the Diagnostic Tools window.
 
-    ![Logpoint data in the diagsession window](../debugger/media/snapshot-logpoint-output.png)
+    ![Logpoint data in the Diagnostic Tools window](../debugger/media/snapshot-logpoint-output.png)
 
     If you choose **Send to application log**, when the logpoint is hit, the message appears anywhere that you can see messages from `System.Diagnostics.Trace` (or `ILogger` in .NET Core), such as [App Insights](/azure/application-insights/app-insights-asp-net-trace-logs).
 

docs/debugger/debug-live-azure-apps-faq.md

@@ -17,27 +17,27 @@ Here is a list of questions that might come up when debugging live Azure applica
 
 #### What is the performance cost of taking a snapshot?
 
-When the Snapshot Debugger captures a snapshot of your app, it is forking the app's process and suspending the forked copy. When you debug a snapshot, you are debugging against the forked copy of the process. This process takes only 10-20 milliseconds but does not copy the full heap of the app. Instead, it copies only the page table and sets pages to copy on write. If some of your app's objects on the heap change, their respective pages are then copied. Each snapshot therefore has a small in-memory cost (on the order of hundreds of kilobytes for most apps).
+When the Snapshot Debugger captures a snapshot of your app, it forks the app's process and suspends the forked copy. When you debug a snapshot, you're debugging against the forked copy of the process. This process takes only 10-20 milliseconds but doesn't copy the full heap of the app. Instead, it copies only the page table and sets pages to copy on write. If some of your app's objects on the heap change, their respective pages are then copied. That's whey each snapshot has a small in-memory cost (on the order of hundreds of kilobytes for most apps).
 
 #### What happens if I have a scaled-out Azure App Service (multiple instances of my app)?
 
-When you have multiple instances of your app, snappoints get applied to every single instance. Only the first snappoint to hit with the conditions specified creates a snapshot. If you have multiple snappoints, subsequent snapshots come from the same instance that created the first snapshot. Logpoints sent to the output window will only show messages from one instance, while logpoints sent to application logs send messages from every instance.
+When you have multiple instances of your app, snappoints get applied to every single instance. Only the first snappoint to hit with the conditions specified creates a snapshot. If you have multiple snappoints, later snapshots come from the same instance that created the first snapshot. Logpoints sent to the output window will only show messages from one instance, while logpoints sent to application logs send messages from every instance.
 
 #### How does the Snapshot Debugger load symbols?
 
-The Snapshot Debugger requires that you have the matching symbols for your application either local or deployed to your Azure App Service. (Embedded PDBs are currently not supported.) The Snapshot Debugger automatically downloads symbols from your Azure App Service. As of Visual Studio 2017 version 15.2, deploying to Azure App Service also deploys your app's symbols.
+The Snapshot Debugger requires that you have the matching symbols for your application either local or deployed to your Azure App Service. (Embedded PDBs are currently not supported.) The Snapshot Debugger automatically downloads symbols from your Azure App Service. Starting with Visual Studio 2017 version 15.2, deploying to Azure App Service also deploys your app's symbols.
 
 #### Does the Snapshot Debugger work against release builds of my application?
 
-Yes - the Snapshot Debugger is intended to work against release builds. When a snappoint is placed in a function, the function is recompiled back to a debug version, making it debuggable. When you stop the Snapshot Debugger, the functions are returned to their release build.
+Yes - the Snapshot Debugger is intended to work against release builds. When a snappoint is placed in a function, the function is recompiled back to a debug version, making it debuggable. Stopping the Snapshot Debugger returns functions to the version of the release build.
 
 #### Can logpoints cause side effects in my production application?
 
-No - any log messages you add to your app are evaluated virtually. They cannot cause any side effects in your application. However, some native properties may not be accessible with logpoints.
+No - any log messages you add to your app are evaluated virtually. They can't cause any side effects in your application. However, some native properties may not be accessible with logpoints.
 
 #### Does the Snapshot Debugger work if my server is under load?
 
-Yes, snapshot debugging can work for servers under load. The Snapshot Debugger throttles and does not capture snapshots in situations where there is a low amount of free memory on your server.
+Yes, snapshot debugging can work for servers under load. The Snapshot Debugger throttles and doesn't capture snapshots in situations where there's a low amount of free memory on your server.
 
 #### How do I uninstall the Snapshot Debugger?
 
@@ -47,6 +47,10 @@ You can uninstall the Snapshot Debugger site extension on your App Service with
 1. Navigate to your App Service's Kudu site (that is, yourappservice.**scm**.azurewebsites.net) and navigate to **Site extensions**.
 1. Click the X on the Snapshot Debugger site extension to remove it.
 
+#### Why are ports opened during a Snapshot Debugger session?
+
+Snapshot Debugger needs to open a set of ports in order to debug the snapshots taken in Azure, these are the same ports required for remote debugging. [You can find the list of ports here](../debugger/remote-debugger-port-assignments.md).
+
 ## See also
 
 - [Debugging in Visual Studio](../debugger/index.md)