Merge remote-tracking branch 'MicrosoftDocs/master'

Author: timeyoutakeit

docs/cross-platform/cross-platform-mobile-development-in-visual-studio.md

@@ -111,7 +111,7 @@ In this tutorial, you will:
 
 1. In *Program.cs*, replace the default code with the following code:
 
-    ```c#
+    ```csharp
     using System;
     using System.Runtime.InteropServices;
 
@@ -178,7 +178,7 @@ In most versions of Visual Studio 2017, you must enable mixed mode debugging for
 
 1. In the C# project, open *Program.cs* and set a breakpoint in the following line of code by clicking in the left margin:
 
-    ```c#
+    ```csharp
     int result = Multiply(7, 7);
     ```
 

docs/debugger/how-to-debug-managed-and-native-code.md

@@ -1,49 +1,45 @@
 ---
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
+ title: Deploy to local folder
+ description: Deploy an app to a local folder
+ services: ""
+ author: mikejo5000
+ ms.service: ""
+ ms.topic: include
+ ms.date: 05/23/2018
+ ms.author: mikejo
+ ms.custom: include file
 ---
+
 1. In the **Solution Explorer**,  right-click the project node and select **Publish** (for Web Forms, **Publish Web App**).
 
-2. In the **Publish** dialog box, select **Folder**, click **Browse**, and create a new folder, **C:\Publish**.
+    If you have previously configured any publishing profiles, the **Publish** pane appears. Click **New profile**.
+
+1. In the **Publish** dialog box, select **Folder**, click **Browse**, and create a new folder, **C:\Publish**.
 
     ![RemoteDBG_Publish_Local](../media/remotedbg_publish_local.png "RemoteDBG_Publish_Local")
 
     For a Web Forms app, choose **Custom** in the Publish dialog box, enter a profile name, and choose **OK**.
 
-3. Click **Publish**.
-
-    Visual Studio publishes the project to the folder. Progress shows in the Output window.
+1. Click **Create profile** in the drop-down list (**Publish** is the default value).
 
-4. In the **Publish** dialog box, click the **Settings** link, and then select the **Settings** tab.
+1. In the **Publish** dialog box, click the **Settings** link, and then select the **Settings** tab.
 
-5. Set the configuration to **Debug**, select **Delete all existing files prior to publish**, and then click **Save**.
+1. Set the configuration to **Debug**, select **Delete all existing files prior to publish**, and then click **Save**.
 
     > [!NOTE]
     > If you use a Release build, you disable debugging in the web.config file when you publish.
 
-6. Click **Publish**.
+1. Click **Publish**.
 
     ![RemoteDBG_Publish_Debug_Config](../media/remotedbg_publish_debug_config.png "RemoteDBG_Publish_Debug_Config")
 
-    The application publishes a **Debug** configuration of the project to the local folder.
+    The application publishes a **Debug** configuration of the project to the local folder. Progress shows in the Output window.
 
-5. Copy the ASP.NET project directory from the Visual Studio computer to the local directory configured for the ASP.NET app (in this example, **C:\Publish**) on the Windows Server computer. In this tutorial, we assume you are copying manually, but you can use other tools like PowerShell, Xcopy, or Robocopy.
+1. Copy the ASP.NET project directory from the Visual Studio computer to the local directory configured for the ASP.NET app (in this example, **C:\Publish**) on the Windows Server computer. In this tutorial, we assume you are copying manually, but you can use other tools like PowerShell, Xcopy, or Robocopy.
 
     > [!CAUTION]
     >  If you need to make changes to the code or rebuild, you must republish and repeat this step. The executable you copied to the remote machine must exactly match your local source and symbols.    If you do not do this you will receive a `cannot find or open the PDB file` warning in Visual Studio when you attempt to debug the process.
 
-6. On the Windows Server, verify that you can run the app correctly by opening the app in your browser.
+1. On the Windows Server, verify that you can run the app correctly by opening the app in your browser.
 
     If the app doesn't run correctly, there may be a mismatch between the version of ASP.NET installed on your server and your Visual Studio machine, or you may have an issue with your IIS or Web site configuration. Recheck earlier steps.

docs/debugger/includes/remote-debugger-deploy-app-local.md

@@ -1,48 +1,46 @@
 ---
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
+ title: Deploy using Web Deploy
+ description: Deploy an app using Web Deploy in Visual Studio
+ services: ""
+ author: mikejo5000
+ ms.service: ""
+ ms.topic: include
+ ms.date: 05/23/2018
+ ms.author: mikejo
+ ms.custom: include file
 ---
+
 If you installed Web Deploy using the Web Platform Installer, you can deploy the app directly from Visual Studio.
 
 1. Start Visual Studio with Administrator privileges, and reopen the project.
 
     Administrator privileges are required to deploy your app using Web Deploy.
 
-2. In the **Solution Explorer**,  right-click the project node and select **Publish**.
+1. In the **Solution Explorer**,  right-click the project node and select **Publish**.
+
+    If you have previously configured any publishing profiles, the **Publish** pane appears. Click **New profile**.
 
-3. For **Select a publish target**, select **IIS, FTP, etc.** and click **Publish**.
+1. For **Select a publish target**, select **IIS, FTP, etc.** and click **Publish**.
 
     ![RemoteDBG_Publish_IISl](../media/remotedbg_iis_profile.png "RemoteDBG_Publish_IIS")
 
-4. Enter the correction configuration parameters for your IIS setup.
+1. Enter the correction configuration parameters for your IIS setup.
 
     ![RemoteDBG_Publish_WebDeployl](../media/remotedbg_iis_webdeploy_config.png "RemoteDBG_Publish_WebDeploy")
 
     If a host name doesn't resolve when you try to validate in the next steps in the **Server** text box, try the IP address. Include `http://` as a prefix in the **Server** field.  Make sure you use port 80 in the **Server** text box, and make sure that port 80 is open in the firewall.
 
-6. Click **Next**, choose a **Debug** configuration, and choose **Remove additional files at destination** under the **File Publish** options.
+1. Click **Next**, choose a **Debug** configuration, and choose **Remove additional files at destination** under the **File Publish** options.
 
     > [!NOTE]
     > If you choose a Release configuration, you disable debugging in the web.config file when you publish.
 
-5. Click **Prev**, and then choose **Validate**. If the connection setup validates, you can try to publish.
+1. Click **Prev**, and then choose **Validate**. If the connection setup validates, you can try to publish.
 
-6. Click **Publish** to publish the app.
+1. Click **Publish** to publish the app.
 
     The Output tab shows you if publishing is successful, and your browser then opens the app.
 
     If you get an error mentioning Web Deploy, recheck the Web Deploy installation steps and make sure the correct ports are open (Web Deploy also requires port 8172 to be open on the server).
 
-    If the app deploys successfully but doesn't run correctly, there may be an issue with your IIS configuration, your ASP.NET installation, or your Web site configuration. On the Windows Server, open the Web site from IIS for more specific error messages, and then recheck earlier steps.
+    If the app deploys successfully but doesn't run correctly, there may be an issue with your IIS configuration, your ASP.NET installation, or your Web site configuration. On the Windows Server, open the Web site from IIS for more specific error messages, and then recheck earlier steps.

docs/debugger/includes/remote-debugger-deploy-app-web-deploy.md

@@ -1,27 +1,22 @@
 ---
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
+ title: Remote debugger download
+ description: Download links for the remote debugger
+ services: ""
+ author: mikejo5000
+ ms.service: ""
+ ms.topic: include
+ ms.date: 05/23/2018
+ ms.author: mikejo
+ ms.custom: include file
 ---
+
 1.  On the device or server machine that you want to debug (rather than the machine running Visual Studio), get the correct version of the remote tools.
 
     |Version|Link|Notes|
     |-|-|-|
-    |Visual Studio 2017 (latest version)|[Remote tools](https://www.visualstudio.com/downloads/?q=remote+tools#remote-tools-for-visual-studio-2017)|Always download the version matching your device operating system (x86 or x64). If enhanced security mode is enabled (Windows Server), you must add new trusted sites if prompted.|
-    |Visual Studio 2017 (older)|[Remote tools](https://my.visualstudio.com/Downloads?q=remote%20tools%20visual%20studio%202017)|Remote tools for earlier releases of Visual Studio 2017 are available from My.VisualStudio.com. If prompted, join the free Visual Studio Dev Essentials group, or sign in with your Visual Studio subscription ID. If enhanced security mode is enabled (Windows Server), you must add new trusted sites if prompted.|
-    |Visual Studio 2015 Update 3|[Remote tools](https://my.visualstudio.com/Downloads?q=remote%20tools%20visual%20studio%202015)|If prompted, join the free Visual Studio Dev Essentials group, or sign in with your Visual Studio subscription ID. If enhanced security mode is enabled (Windows Server), you must add new trusted sites if prompted.|
-    |Visual Studio 2015 (older)|[Remote tools](https://my.visualstudio.com/Downloads?q=remote%20tools%20visual%20studio%202015)|If prompted, join the free Visual Studio Dev Essentials group, or sign in with your Visual Studio subscription ID. If enhanced security mode is enabled (Windows Server), you must add new trusted sites if prompted.|
+    |Visual Studio 2017 (latest version)|[Remote tools](https://www.visualstudio.com/downloads/?q=remote+tools#remote-tools-for-visual-studio-2017)|Always download the version matching your device operating system (x86 or x64). On Windows Server, see [Unblock the file download](../../debugger/remote-debugging.md#unblock_msvsmon) for help to download the remote tools.|
+    |Visual Studio 2017 (older)|[Remote tools](https://my.visualstudio.com/Downloads?q=remote%20tools%20visual%20studio%202017)|Remote tools for earlier releases of Visual Studio 2017 are available from My.VisualStudio.com. If prompted, join the free Visual Studio Dev Essentials group, or sign in with your Visual Studio subscription ID. On Windows Server, see [Unblock the file download](../../debugger/remote-debugging.md#unblock_msvsmon) for help to download the remote tools.|
+    |Visual Studio 2015 (older)|[Remote tools](https://my.visualstudio.com/Downloads?q=remote%20tools%20visual%20studio%202015)|If prompted, join the free Visual Studio Dev Essentials group, or sign in with your Visual Studio subscription ID. On Windows Server, see [Unblock the file download](../../debugger/remote-debugging.md#unblock_msvsmon) for help to download the remote tools.|
     |Visual Studio 2013|[Remote tools](https://msdn.microsoft.com/library/bt727f1t(v=vs.120).aspx#BKMK_Installing_the_Remote_Tools)|Download page in Visual Studio 2013 documentation|
     |Visual Studio 2012|[Remote tools](https://msdn.microsoft.com/library/bt727f1t(v=vs.110).aspx#BKMK_Installing_the_Remote_Tools)|Download page in Visual Studio 2012 documentation|
 

docs/debugger/includes/remote-debugger-download.md

@@ -20,6 +20,6 @@ For Windows Server operating systems, use the **Add Roles and Features** wizard
 
 ![The Web Server IIS role is selected in the Select server roles step.](../media/remotedbg-server-roles-ws2012.png)
 
-On the **Role services** step, select the IIS role services you desire or accept the default role services provided.
+On the **Role services** step, select the IIS role services you desire or accept the default role services provided. If you plan to deploy using Web Deploy, make sure that **IIS Management Scripts and Tools** is selected.
 
 Proceed through the confirmation steps to install the web server role and services. A server/IIS restart is not required after installing the Web Server (IIS) role.

docs/debugger/includes/remote-debugger-install-iis-role.md

@@ -36,7 +36,7 @@ The Visual Studio debugger provides many powerful features to help you debug you
 
 1. In Solution Explorer, open About.cshtml.cs (under Pages/About.cshtml) and replace the following code
 
-    ```c#
+    ```csharp
     public void OnGet()
     {
         Message = "Your application description page.";
@@ -45,7 +45,7 @@ The Visual Studio debugger provides many powerful features to help you debug you
 
     with this code:
 
-    ```c#
+    ```csharp
     public void OnGet()
     {
         LinkedList<int> result = doWork();

docs/debugger/media/remotedbg-blocked-content.png

@@ -32,7 +32,7 @@ The Visual Studio debugger provides many powerful features to help you debug you
 
 4. In Program.cs or Module1.vb, replace the following code
 
-    ```c#
+    ```csharp
     class Program
     {
         static void Main(string[] args)
@@ -50,7 +50,7 @@ The Visual Studio debugger provides many powerful features to help you debug you
 
     with this code:
 
-    ```c#
+    ```csharp
     class Program
     {
         private static void doWork()