Merge branch 'master' into ghogen-coauth

Author: ghogen

.openpublishing.publish.config.json

@@ -53,6 +53,7 @@
   "git_repository_url_open_to_public_contributors": "https://github.com/Microsoft/visualstudio-docs",
   "git_repository_branch_open_to_public_contributors": "master",
   "skip_source_output_uploading": false,
+  "need_preview_pull_request": true,
   "dependent_repositories": [
     {
       "path_to_root": "_themes",
@@ -70,5 +71,6 @@
       }
     }
   ],
+  "branch_target_mapping": {},
   "need_generate_pdf_url_template": false
 }

docs/cross-platform/visual-studio-emulator-for-android.md

@@ -1,7 +1,7 @@
 ---
 title: "Visual Studio Emulator for Android | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "07/17/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -33,23 +33,10 @@ The Visual Studio Emulator for Android is a desktop application that emulates an
 
  The Visual Studio Emulator for Android is designed to provide comparable performance to an actual device. Before you publish your app, however, we recommend that you test your app on a physical device.  
 
- You can test your app on a unique device profile for each of the Android platforms, screen resolutions, and other hardware properties supported by Visual Studio Emulator for Android.  
-  
- This topic contains the following sections.  
-  
--   [Installing and uninstalling](#Installing)  
-  
--   [System Requirements and backward compatibility](#Requirements)  
-  
--   [Networking in the Visual Studio Emulator for Android](#Networking)  
-  
--   [Configure the Visual Studio Emulator for Android](#Configuring)  
-  
--   [Features that you can test in the emulator](#FeaturesTest)  
-  
--   [Features that you can't test in the emulator](#FeaturesNonTest)  
-  
--   [Support Resources](#Support)  
+ You can test your app on a unique device profile for each of the Android platforms, screen resolutions, and other hardware properties supported by Visual Studio Emulator for Android.
+
+> [!NOTE]
+> The Google Android emulator is recommended for use with the Visual Studio Tools for Apache Cordova. For more information, see [Run your Apache Cordova app on Android](/visualstudio/cross-platform/tools-for-cordova/run-your-app/run-app-android#a-idgoogle-android-emulatora-run-on-the-google-android-emulator).
   
 ##  <a name="Installing"></a> Installing and uninstalling  
  Installing  

docs/debugger/debug-installed-app-package.md

@@ -53,9 +53,7 @@ For more information about these features, see the blog post on updates for [deb
 
 ## Debug an Installed App Package or Running App on a Local Machine or Device
 
-1. On your Windows 10 device, enable [developer mode](/windows/uwp/get-started/enable-your-device-for-development).
-
-2. With your UWP project open in Visual Studio, select **Debug**, **Other Debug Targets**, and then **Debug Installed App Package**.
+1. With your UWP project open in Visual Studio, select **Debug**, **Other Debug Targets**, and then **Debug Installed App Package**.
 
 2. Select either **Local Machine** or **Device**.
 

docs/debugger/debugger-basics.md

@@ -1,7 +1,7 @@
 ---
 title: "Debugger Basics | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "07/11/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 

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

@@ -34,7 +34,7 @@ You must have administrative permissions on the remote computer.
 
      ![RemoteDebuggerWindow](../media/remotedebuggerwindow.png "RemoteDebuggerWindow")
 
-     The remote debugger is now waiting for a connection. Make a note of the server name and port number that is displayed, because you need this information later for configuration in Visual Studio.  
+     The remote debugger is now waiting for a connection. Make a note of the server name and port number that is displayed, because this must match the configuration you later use in Visual Studio.  
 
  When you are finished debugging and need to stop the remote debugger, click **File / Exit** on the window. You can restart it from the **Start** menu or from the command line:  
 

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

@@ -30,7 +30,7 @@ If you installed Web Deploy using the Web Platform Installer, you can deploy the
 
     ![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. Make sure you use port 80 in the **Server** text box, and make sure that port 80 is open in the firewall.
+    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.
 

docs/debugger/index.md

@@ -64,7 +64,7 @@ The Visual Studio debugger helps you observe the run-time behavior of your progr
         </a>
     </li>
         <li>
-        <a href="https://docs.microsoft.com/en-us/visualstudio/debugger/getting-started-with-the-debugger.md#video">
+        <a href="https://docs.microsoft.com/en-us/visualstudio/debugger/getting-started-with-the-debugger#video">
         <div class="cardSize">
             <div class="cardPadding">
                 <div class="card">

docs/debugger/intellitrace-features.md

@@ -59,7 +59,10 @@ You can use IntelliTrace to record events and method calls your application, whi
  If you're debugging, stop debugging. Go to **Tools / Options / IntelliTrace / IntelliTrace Events**. Choose the events you want IntelliTrace to record.  
 
 ##  <a name="GoingFurther"></a> Collect IntelliTrace events and call information  
- This isn't enabled by default, but IntelliTrace can record method calls along with events. To enable collection of method calls go to **Tools / Options / IntelliTrace / General**, and select **IntelliTrace events and call information**.  
+ This isn't enabled by default, but IntelliTrace can record method calls along with events. To enable collection of method calls go to **Tools / Options / IntelliTrace / General**, and select **IntelliTrace events and call information**.
+
+> [!NOTE]
+> Call information is not currently available for ASP.NET Core apps. 
   
  This lets you see the call stack history and step backward and forward through calls in your code. IntelliTrace records data such as method names, method entry and exit points, and certain parameter values and return values.  
 

docs/debugger/intellitrace.md

@@ -1,7 +1,7 @@
 ---
 title: "IntelliTrace | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "07/18/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -66,12 +66,12 @@ You can spend less time debugging your application when you use IntelliTrace to
 
 |||  
 |-|-|  
-|**Supported**|-   Visual Basic and Visual C# applications that use .NET Framework 2.0 or higher versions.<br />     You can debug most applications, including ASP.NET, Microsoft Azure, Windows Forms, WCF, WPF, Windows Workflow, SharePoint 2010, SharePoint 2013, and 64-bit apps.<br />     To debug SharePoint applications with IntelliTrace, see [Walkthrough: Debugging a SharePoint Application by Using IntelliTrace](../sharepoint/walkthrough-debugging-a-sharepoint-application-by-using-intellitrace.md).<br />     To debug Microsoft Azure apps with IntelliTrace, see [Debugging a Published Cloud Service with IntelliTrace and Visual Studio](http://go.microsoft.com/fwlink/?LinkID=262248).|  
+|**Supported**|-   Visual Basic and Visual C# applications that use .NET Framework 2.0 or higher versions.<br />     You can debug most applications, including ASP.NET, Microsoft Azure, Windows Forms, WCF, WPF, Windows Workflow, SharePoint 2010, SharePoint 2013, and 64-bit apps.<br />     To debug SharePoint applications with IntelliTrace, see [Walkthrough: Debugging a SharePoint Application by Using IntelliTrace](../sharepoint/walkthrough-debugging-a-sharepoint-application-by-using-intellitrace.md).<br />     To debug Microsoft Azure apps with IntelliTrace, see [Debugging a Published Cloud Service with IntelliTrace and Visual Studio](/azure/vs-azure-tools-intellitrace-debug-published-cloud-services).|  
 |**Limited support**|-   F# apps on an experimental basis<br />-   Windows Store apps supported for events only|  
 |**Not supported**|-   C++, other languages, and script<br />-   Windows Services, Silverlight, Xbox, or [!INCLUDE[winmobile](../debugger/includes/winmobile_md.md)] apps|  
 
 > [!NOTE]
->  If you want to debug a process that is already running, you can't use IntelliTrace. You must start IntelliTrace when the process starts.  
+>  If you want to debug a process that is already running, you can collect IntelliTrace events only (no call information). You can attach to a 32-bit or 64-bit process on the local machine only. Events that occur before you attach to the process are not collected.
   
 ##  <a name="IntelliTraceVSTraditional"></a> Why debug with IntelliTrace?  
  Traditional or *live* debugging shows only your application's current state, with limited data about past events. You either have to infer these events based on the application's current state, or you have to recreate these events by rerunning your application.  
@@ -82,7 +82,7 @@ You can spend less time debugging your application when you use IntelliTrace to
 
  You can save IntelliTrace data from these sources:  
 
--   An IntelliTrace session in Visual Studio 2015 Enterprise or previous versions of Visual Studio Ultimate.  
+-   An IntelliTrace session in Visual Studio 2017 Enterprise, Visual Studio 2015 Enterprise, or previous versions of Visual Studio Ultimate.  
 
 -   A test session in Microsoft Test Manager  
 
@@ -139,13 +139,11 @@ You can spend less time debugging your application when you use IntelliTrace to
 
      By default, IntelliTrace records the most common .NET Framework events. For example:  
 
-    -   For a File Access event, IntelliTrace collects the file name.  
-  
     -   For a Check Checkbox event, IntelliTrace collects the checkbox state and text.  
 
 -   **SharePoint 2010 and SharePoint 2013 application events**  
 
-     You can record user profile events and a subset of Unified Logging System (ULS) events for SharePoint 2010 and 2013 applications running outside Visual Studio. You can save these events to an .iTrace file. Requires Visual Studio Enterprise 2015, a previous version of Visual Studio Ultimate, or [Microsoft Monitoring Agent](http://go.microsoft.com/fwlink/?LinkId=320384) running in **Trace** mode.  
+     You can record user profile events and a subset of Unified Logging System (ULS) events for SharePoint 2010 and 2013 applications running outside Visual Studio. You can save these events to an .iTrace file. Requires Visual Studio Enterprise 2017, Visual Studio Enterprise 2015, a previous version of Visual Studio Ultimate, or [Microsoft Monitoring Agent](http://go.microsoft.com/fwlink/?LinkId=320384) running in **Trace** mode.  
 
      When you open the .iTrace file, enter a SharePoint correlation ID to find its matching web request, view the recorded events, and start debugging from a specific event. If the file contains unhandled exceptions, you can choose a correlation ID to start debugging an exception.  
 

docs/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md

@@ -1,7 +1,7 @@
 ---
 title: "Remote Debug ASP.NET on a Remote IIS Computer | Microsoft Docs"
-ms.custom: "H1Hack27Feb2017"
-ms.date: "03/22/2017"
+ms.custom: "remotedebugging"
+ms.date: "07/26/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -41,7 +41,7 @@ There are many ways you can deploy and debug on IIS. Here are a few of the commo
 |-|-|-|
 |[Azure App Service](https://docs.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs)|From Visual Studio, you can quickly publish and debug your app to a fully provisioned instance of IIS. However, the configuration of IIS is preset and you cannot customize it. To use this option, choose **Microsoft Azure App Service** from the **Publish** dialog box, follow the prompts to publish, and debug in **Server Explorer** by right-clicking on the App Service instance, and choosing **Attach Debugger**.|
 |[Azure VM](../debugger/remote-debugging-azure.md)|If you want more control of the IIS configuration, you can [install the IIS role on an Azure VM](https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-hero-role), download and run the RDP file, and open ports in the Network security group, as described in the [Azure VM tutorial](../debugger/remote-debugging-azure.md).|
-|[Windows Server](#bkmk_configureII)|Follow the steps in this tutorial to remote debug on Windows Server or a VM running Windows Server.|
+|[Windows Server](#bkmk_configureIIS)|Follow the steps in this tutorial to remote debug on Windows Server or a VM running Windows Server.|
 
 ## Create the ASP.NET 4.5.2 application on the Visual Studio computer
 
@@ -87,13 +87,21 @@ On Windows Server 2012 R2, see [IIS Configuration](https://docs.asp.net/en/lates
 
 ## <a name="BKMK_deploy_asp_net"></a> Configure ASP.NET Web site on the Windows Server computer
 
-1. Open the **Internet Information Services (IIS) Manager** and go to **Sites**.
+1. Open Windows Explorer and create a new folder, **C:\Publish**, where you will later deploy the ASP.NET project.
 
-2. Right-click the **Default Web Site** node and select **Add Application**.
+2. Open the **Internet Information Services (IIS) Manager**. (In the left pane of Server Manager, select **IIS**. Right-click the server and select **Internet Information Services (IIS) Manager**.)
 
-3. Set the **Alias** field to **MyASPApp** and the Application pool field to **ASP.NET v4.0** (ASP.NET 4.5 is not an option for the Application pool). Set the **Physical path** to **C:\Publish** (where you will later deploy the ASP.NET project).
+3. Under **Connections** in the left pane, go to **Sites**.
 
-4. With the site selected in the IIS Manager, choose **Edit Permissions**, and make sure that IUSR, IIS_IUSRS, or the user configured for the Application Pool is an authorized user with Read & Execute rights. If none of these are present, add IUSR as a user with Read & Execute rights.
+4. Select the **Default Web Site**, choose **Basic Settings**, and set the **Physical path** to **C:\Publish**.
+
+5. Right-click the **Default Web Site** node and select **Add Application**.
+
+6. Set the **Alias** field to **MyASPApp**, accept the default Application Pool (**DefaultAppPool**), and set the **Physical path** to **C:\Publish**.
+
+7. Under **Connections**, select **Application Pools**. Open **DefaultAppPool** and set the Application pool field to **ASP.NET v4.0** (ASP.NET 4.5 is not an option for the Application pool).
+
+8. With the site selected in the IIS Manager, choose **Edit Permissions**, and make sure that IUSR, IIS_IUSRS, or the user configured for the Application Pool is an authorized user with Read & Execute rights. If none of these are present, add IUSR as a user with Read & Execute rights.
 
 ## <a name="bkmk_webdeploy"></a> (Optional) Publish and deploy the app using Web Deploy from Visual Studio
 

docs/debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md

@@ -1,7 +1,7 @@
 ---
 title: "Remote Debug ASP.NET Core on a Remote IIS Computer | Microsoft Docs"
-ms.custom: "H1Hack27Feb2017"
-ms.date: "03/22/2017"
+ms.custom: "remotedebugging"
+ms.date: "07/26/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -42,7 +42,7 @@ There are many ways you can deploy and debug on IIS. Here are a few of the commo
 |-|-|-|
 |[Azure App Service](https://docs.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs)|From Visual Studio, you can quickly publish and debug your app to a fully provisioned instance of IIS. However, the configuration of IIS is preset and you cannot customize it. To use this option, choose **Microsoft Azure App Service** from the **Publish** dialog box, follow the prompts to publish, and debug in **Server Explorer** by right-clicking on the App Service instance, and choosing **Attach Debugger**.|
 |[Azure VM](../debugger/remote-debugging-azure.md)|If you want more control of the IIS configuration, you can [install the IIS role on an Azure VM](https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-hero-role), download and run the RDP file, and open ports in the Network security group, as described in the [Azure VM tutorial](../debugger/remote-debugging-azure.md).|
-|[Windows Server](#bkmk_configureII)|Follow the steps in this tutorial to remote debug on Windows Server or a VM running Windows Server.|
+|[Windows Server](#bkmk_configureIIS)|Follow the steps in this tutorial to remote debug on Windows Server or a VM running Windows Server.|
 
 ## Create the ASP.NET Core application on the Visual Studio 2017 computer 
 
@@ -82,13 +82,21 @@ When you download the software, you may get requests to grant permission to load
 
 ## <a name="BKMK_deploy_asp_net"></a> Configure ASP.NET Web site on the Windows Server computer
 
-1. Open the **Internet Information Services (IIS) Manager** and go to **Sites**.
+1. Open Windows Explorer and create a new folder, **C:\Publish**, where you will later deploy the ASP.NET project.
 
-2. Right-click the **Default Web Site** node and select **Add Application**.
+2. Open the **Internet Information Services (IIS) Manager**. (In the left pane of Server Manager, select **IIS**. Right-click the server and select **Internet Information Services (IIS) Manager**.)
 
-3. Set the **Alias** field to **MyASPApp** and the Application pool field to **No Managed Code**. Set the **Physical path** to **C:\Publish** (where you will later deploy the ASP.NET project).
+3. Under **Connections** in the left pane, go to **Sites**.
 
-4. With the site selected in the IIS Manager, choose **Edit Permissions**, and make sure that IUSR, IIS_IUSRS, or the user configured for the Application Pool is an authorized user with Read & Execute rights.
+4. Select the **Default Web Site**, choose **Basic Settings**, and set the **Physical path** to **C:\Publish**.
+
+4. Right-click the **Default Web Site** node and select **Add Application**.
+
+5. Set the **Alias** field to **MyASPApp**, accept the default Application Pool (**DefaultAppPool**), and set the **Physical path** to **C:\Publish**.
+
+6. Under **Connections**, select **Application Pools**. Open **DefaultAppPool** and set the Application pool field to **No Managed Code**.
+
+7. Right-click the new site in the IIS Manager, choose **Edit Permissions**, and make sure that IUSR, IIS_IUSRS, or the user configured for access to the web app is an authorized user with Read & Execute rights.
 
     If you don't see one of these users with access, go through steps to add IUSR as a user with Read & Execute rights.
 

docs/debugger/remote-debugging-azure.md

@@ -1,7 +1,7 @@
 ---
 title: "Remote Debug ASP.NET Core on IIS and Azure | Microsoft Docs"
-ms.custom: "H1Hack27Feb2017"
-ms.date: "03/31/2017"
+ms.custom: "remotedebugging"
+ms.date: "07/26/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -42,6 +42,9 @@ This topic shows how to:
 
 * Remote debug ASP.NET Core on an Azure VM
 
+> [!NOTE]
+> To debug ASP.NET Core on Azure Service Fabric, see [Debug a remote Service Fabric application](/azure/service-fabric/service-fabric-debugging-your-application#debug-a-remote-service-fabric-application).
+
 ## Create the ASP.NET Core application on the Visual Studio 2017 computer 
 
 1. Create a new ASP.NET Core application. (Choose **File / New / Project**, then select **Visual C# / Web / ASP.NET Core Web Application (.NET Core)**)

docs/debugger/remote-debugging-cpp.md

@@ -1,6 +1,6 @@
 ---
 title: "Remote Debug a Visual C++ Project | Microsoft Docs"
-ms.custom: "H1Hack27Feb2017"
+ms.custom: "remotedebugging"
 ms.date: "05/18/2017"
 ms.reviewer: ""
 ms.suite: ""
@@ -54,7 +54,7 @@ For information about remote debugging apps with Azure backends, see [Remote deb
 
 [!INCLUDE [remote-debugger-configuration](../debugger/includes/remote-debugger-configuration.md)]
 
-## Remote debug a Visual C++ project  
+## <a name="remote_cplusplus"></a> Remote debug a Visual C++ project  
  In the following procedure, the name and path of the project is C:\remotetemp\MyMfc, and the name of the remote computer is **MJO-DL**.  
 
 1.  Create an MFC application named **mymfc.**