Merge pull request #579 from MicrosoftDocs/mikejo-br1

intellitrace, metadata updates

Author: Mikejo5000

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/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md

@@ -1,6 +1,6 @@
 ---
 title: "Remote Debug ASP.NET on a Remote IIS Computer | Microsoft Docs"
-ms.custom: "H1Hack27Feb2017"
+ms.custom: "remotedebugging"
 ms.date: "07/26/2017"
 ms.reviewer: ""
 ms.suite: ""
@@ -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
 

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 
 

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: ""

docs/debugger/remote-debugging-csharp.md

@@ -1,6 +1,6 @@
 ---
 title: "Remote Debug a C# or VB Project in Visual Studio | Microsoft Docs"
-ms.custom: "H1Hack27Feb2017"
+ms.custom: "remotedebugging"
 ms.date: "05/18/2017"
 ms.reviewer: ""
 ms.suite: ""

docs/debugger/remote-debugging.md

@@ -1,7 +1,7 @@
 ---
 title: "Remote debugging in Visual Studio | Microsoft Docs"
-ms.custom: "H1Hack27Feb2017"
-ms.date: "04/03/2017"
+ms.custom: "remotedebugging"
+ms.date: "07/26/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -51,7 +51,7 @@ For in-depth instructions on remote debugging, see these topics.
 |C++|[Remote Debugging a C++ Project](remote-debugging-cpp.md)|
 |Universal Windows Apps (UWP)|[Debug an Installed App Package](debug-installed-app-package.md)|
 |Azure|[Remote Debugging ASP.NET on Azure](remote-debugging-azure.md)|
-|Azure Cloud Service|[Debugging an Azure cloud service](https://docs.microsoft.com/en-us/azure/vs-azure-tools-debug-cloud-services-virtual-machines)|
+|Azure Service Fabric|[Debug a remote Service Fabric application](/azure/service-fabric/service-fabric-debugging-your-application#debug-a-remote-service-fabric-application).|
 
 If you just want to download and install the remote debugger and don't need any additional instructions for your scenario, follow the steps in this article.
 

docs/debugger/unable-to-connect-to-the-microsoft-visual-studio-remote-debugging-monitor.md

@@ -48,6 +48,7 @@ This message may occur because the remote debugging monitor is not properly set
 The `Unable to Connect to the Microsoft Visual Studio Remote Debugging Monitor` message is generic. Usually, a more specific message is included in the error string and that may help you identify the cause of the problem or search for a more exact fix. Here are a few of the more common error messages that are appended to the main error message:
 
 - [The debugger cannot connect to the remote computer. The debugger was unable to resolve the specified computer name](#cannot_connect)
+- [Connection request was rejected by the remote debugger](#rejected)
 - [There is no server by the specified name running on the remote computer](#no_server)
 - [The requested name was valid, but no data of the requested type was found](#valid_name)
 - [The Visual Studio Remote Debugger on the target computer cannot connect back to this computer](#cant_connect_back)
@@ -61,6 +62,12 @@ An invalid computer name was entered in the **Attach to Process** dialog box or
 
 If correcting the computer name does not resolve this error, see [The remote machine is not reachable](#dns).
 
+## <a name="rejected"></a> Connection request was rejected by the remote debugger
+
+In the **Attach to Process** dialog box or in the project properties, make sure that the remote computer name and the port number matches the name and port number shown in the remote debugger window. If incorrect, fix and try again.
+
+If these values are correct and the message mentions **Windows Authentication** mode, check that the remote debugger is in the correct authentication mode (**Tools / Options**).
+
 ## <a name="no_server"></a> There is no server by the specified name running on the remote computer
 
 Visual Studio could not connect to the remote debugger. This message may occur for several reasons:

docs/debugger/using-saved-intellitrace-data.md

@@ -84,13 +84,14 @@ Go to specific points in your application's execution when you start debugging f
 
 |**Section**|**Contains**|**Collection Source**|  
 |-----------------|------------------|---------------------------|  
-|[Performance Violations](#Performance)|Performance events with function calls that exceed the configured threshold|Microsoft Monitoring Agent, either alone or with System Center 2012 R2 Operations Manager for ASP.NET web apps hosted on IIS|  
+|[Performance Violations](#Performance)|Performance events with function calls that exceed the configured threshold|Microsoft Monitoring Agent, either standalone collector or with System Center 2012 R2 Operations Manager for ASP.NET web apps hosted on IIS|  
 |[Exception Data](#ExceptionData)|Exceptions, including the full call stack for each exception|All sources|  
-|[Analysis](#Analysis)|For SharePoint 2010 and SharePoint 2013 applications only. Diagnose IntelliTrace and SharePoint events, such as debugger events, ULS events, unhandled exceptions, and other data that the Microsoft Monitoring Agent recorded.|Microsoft Monitoring Agent, either alone or with System Center 2012 R2 Operations Manager|  
+|[Analysis](#Analysis)|For SharePoint 2010 and SharePoint 2013 applications only. Diagnose IntelliTrace and SharePoint events, such as debugger events, ULS events, unhandled exceptions, and other data that the Microsoft Monitoring Agent recorded.|Microsoft Monitoring Agent, either standalone collector or with System Center 2012 R2 Operations Manager|  
 |[System Info](#SystemInfo)|Settings and specifications of the host system|All sources|  
 |[Threads List](#ThreadsList)|Threads that ran during collection|All sources|  
 |[Test Data](#TestData)|Test steps and their results from a test session|Test Manager|  
-|[Modules](#Modules)|Modules that the target process loaded in the order that they loaded.|All sources|  
+|[Modules](#Modules)|Modules that the target process loaded in the order that they loaded.|All sources| 
+|[Web Request](#Modules)|Web request data for production IIS web applications and SharePoint 2010 and SharePoint 2013|Microsoft Monitoring Agent and the standalone collector| 
 
  Here's some tips to help you find information in each section:  
 

docs/debugger/walkthrough-using-intellitrace.md

@@ -93,7 +93,10 @@ You can use IntelliTrace to collect information about specific events or categor
 8.  If you didn't find the bug, try examining other events leading up to the bug. You can also have IntelliTrace record call information so you can step through function calls.  
 
 ## Using IntelliTrace with events and function calls  
- IntelliTrace can record function calls along with events. This lets you see the call stack history and step backward and forward through calls in your code. IntelliTrace records data such as function names, function entry and exit points, and certain parameter values and return values. See [IntelliTrace Features](../debugger/intellitrace-features.md).  
+ IntelliTrace can record function calls along with events. This lets you see the call stack history and step backward and forward through calls in your code. IntelliTrace records data such as function names, function entry and exit points, and certain parameter values and return values. See [IntelliTrace Features](../debugger/intellitrace-features.md).
+
+> [!NOTE]
+> Call information is not currently available for ASP.NET Core apps. 
 
 1.  Turn on call collection. (On **Tools / Options / IntelliTrace / General**, select **IntelliTrace events and call information**. IntelliTrace will start collecting this information when the next debugging session starts.