Merge pull request #2976 from Mikejo5000/mikejo-br12

IntelliTrace updates

Author: GitHubber17

.openpublishing.redirection.json

@@ -700,6 +700,11 @@
             "redirect_url": "/visualstudio/debugger/index",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/debugger/how-to-use-intellitrace-step-back.md",
+            "redirect_url": "/visualstudio/debugger/view-historical-application-state",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/deployment/installshield-limited-edition.md",
             "redirect_url": "/visualstudio/deployment/deploying-applications-services-and-components",

docs/debugger/debugger-feature-tour.md

@@ -205,7 +205,7 @@ You can navigate and view snapshots by using the **Step Backward** and **Step Fo
 
 ![Step Backward and Forward Buttons](../debugger/media/intellitrace-step-back-icons-description.png  "Step Backward and Forward buttons")
 
-For more information, see the [View snapshots using IntelliTrace step-back](../debugger/how-to-use-intellitrace-step-back.md) page.
+For more information, see the [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md) page.
 
 ## Next steps
 

docs/debugger/diagnose-problems-after-deployment.md

@@ -11,7 +11,7 @@ manager: douge
 ms.workload:
   - "multiple"
 ---
-# Diagnose problems after deployment
+# Diagnose problems after deployment using IntelliTrace
 
 To diagnose issues in your ASP.NET web app after deployment by using IntelliTrace, include build information with your release to let Visual Studio automatically find the correct source files and symbol files that are required to debug the IntelliTrace log.
 
@@ -21,48 +21,27 @@ To diagnose issues in your ASP.NET web app after deployment by using IntelliTrac
 
  **You'll need:**
 
--   Visual Studio 2017, Visual Studio 2015, or Team Foundation Server 2017, 2015, 2013, 2012, or 2010 to set up your build
+-   Visual Studio, Azure DevOps, or Team Foundation Server 2017, 2015, 2013, 2012, or 2010 to set up your build
 
 -   Microsoft Monitoring Agent to monitor your app and record diagnostic data
 
 -   Visual Studio Enterprise (but not Professional or Community editions) to review diagnostic data and debug your code with IntelliTrace
 
 ##  <a name="SetUpBuild"></a> Step 1: Include build information with your release
- Set up your build process to create a build manifest (BuildInfo.config file) for your web project and include this manifest with your release. This manifest contains information about the project, source control, and build system that were used to create a specific build. This information helps Visual Studio find the matching source and symbols after you open the IntelliTrace log to review the recorded events.
+ Set up your build process to create a build manifest (*BuildInfo.config* file) for your web project and include this manifest with your release. This manifest contains information about the project, source control, and build system that were used to create a specific build. This information helps Visual Studio find the matching source and symbols after you open the IntelliTrace log to review the recorded events.
 
 ###  <a name="AutomatedBuild"></a> Create the build manifest for an automated build using Team Foundation Server
 
  Follow these steps whether you use Team Foundation Version Control or Git.
 
- ####  <a name="TFS2017"></a> Team Foundation Server 2017
+####  <a name="TFS2017"></a> Azure DevOps and Team Foundation Server 2017
 
- Set up your build pipeline to add the locations of your source, build, and symbols to the build manifest (BuildInfo.config file). Team Foundation Build automatically creates this file and puts it in your project's output folder.
-
-1.  If you already have a build pipeline using the ASP.NET Core (.NET Framework) template, you can either [Edit your build pipeline or create a new build pipeline.](/azure/devops/pipelines/get-started-designer?view=vsts)
-
-     ![View build pipeline in TFS 2017](../debugger/media/ffr_tfs2017viewbuilddefinition.png "FFR_TFS2013ViewBuildDefinition")
-
-2.  If you create a new template, choose the ASP.NET Core (.NET Framework) template.
-
-     ![Choose build process template &#45; TFS 2017](../debugger/media/ffr_tfs2017buildprocesstemplate.png "FFR_TFS2013BuildProcessTemplate")
+Visual Studio 2017 does not include the *BuildInfo.config* file, which was deprecated and then removed. To debug ASP.NET web apps after deployment, use one of the following methods:
 
-3.  Specify where to save the symbols (PDB) file so that your source is indexed automatically.
-
-     If you use a custom template, make sure the template has an activity to index your source. You'll later add an MSBuild argument to specify where to save the symbols files.
+* For deployment to Azure, use [Application Insights](https://docs.microsoft.com/en-us/azure/application-insights/).
 
-     ![Set up symbols path in build pipeline TFS 2017](../debugger/media/ffr_tfs2017builddefsymbolspath.png "FFR_TFS2013BuildDefSymbolsPath")
-
-     For more about symbols, see [Publish symbol data](/azure/devops/pipelines/tasks/build/index-sources-publish-symbols?view=vsts).
+* If you need to use IntelliTrace, open the project in Visual Studio and load the symbol files from the matching build. You can load symbol files from the **Modules** window or by configuring symbols in **Tools** > **Options** > **Debugging** > **Symbols**.
 
-4.  Add this MSBuild argument to include your TFS and symbols locations in the build manifest file:
-
-     **/p:IncludeServerNameInBuildInfo=True**
-
-     Anyone who can access your web server can see these locations in the build manifest. Make sure that your source server is secure.
-
-6.  Run a new build.
-
-    Go to [Step 2: Release your app](#DeployRelease)
 
 ####  <a name="TFS2013"></a> Team Foundation Server 2013
  Set up your build pipeline to add the locations of your source, build, and symbols to the build manifest (BuildInfo.config file). Team Foundation Build automatically creates this file and puts it in your project's output folder.

docs/debugger/historical-debugging-inspect-app.md

@@ -73,5 +73,5 @@ private static int AddInt(int add)
 
 This procedure just scratched the surface of what you can do with historical debugging.
 
-- To view snapshots while debugging, see [View snapshots using IntelliTrace step-back](../debugger/how-to-use-intellitrace-step-back.md).
+- To view snapshots while debugging, see [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md).
 - To find out more about the different settings and the effects of the different buttons in the navigation gutter, see [IntelliTrace Features](../debugger/intellitrace-features.md).

docs/debugger/historical-debugging.md

@@ -26,6 +26,6 @@ Historical debugging is a mode of debugging that depends on the information coll
 ## How do I start using historical debugging?  
  IntelliTrace is on by default. All you have to do is decide which events and function calls are of interest to you, and whether you want to view snapshots of your full application state. For more information about defining what you want to look for, see [IntelliTrace Features](../debugger/intellitrace-features.md).  
 
- - To view snapshots with historical debugging, see [View snapshots using IntelliTrace step-back](../debugger/how-to-use-intellitrace-step-back.md)
+ - To view snapshots with historical debugging, see [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md)
  - To learn how to inspect variables and navigate code, see [Inspect your app with historical debugging](../debugger/historical-debugging-inspect-app.md)
  - To learn more about debugging with IntelliTrace events, see [Walkthrough: Using IntelliTrace](../debugger/walkthrough-using-intellitrace.md).

docs/debugger/index.md

@@ -104,7 +104,7 @@ The Visual Studio debugger helps you observe the run-time behavior of your progr
         </a>
     </li>
     <li>
-        <a href="https://docs.microsoft.com/visualstudio/debugger/how-to-use-intellitrace-step-back">
+        <a href="https://docs.microsoft.com/visualstudio/debugger/view-historical-application-state">
         <div class="cardSize">
             <div class="cardPadding">
                 <div class="card">
@@ -114,7 +114,7 @@ The Visual Studio debugger helps you observe the run-time behavior of your progr
                         </div>
                     </div>
                     <div class="cardText">
-                        <h3>View IntelliTrace snapshots (Visual Studio Enterprise)</h3>
+                        <h3>Inspect previous app states (Visual Studio Enterprise)</h3>
                     </div>
                 </div>
             </div>

docs/debugger/intellitrace-features.md

@@ -44,7 +44,7 @@ If you're debugging, stop debugging. Go to **Tools > Options > IntelliTrace > In
 
 ## <a name="Snapshots"></a> Collect snapshots
 
-This isn't enabled by default, but IntelliTrace can capture snapshots of your application at every breakpoint and debugger step event, and you can view these snapshots in a historical debugging session. A snapshot gives you a view of your full application state. To enable the capture of snapshots, go to **Tools > Options > IntelliTrace > General**, and select **IntelliTrace snapshots (managed and native)**. For more information, see [View snapshots using IntelliTrace step-back](../debugger/how-to-use-intellitrace-step-back.md)
+This isn't enabled by default, but IntelliTrace can capture snapshots of your application at every breakpoint and debugger step event, and you can view these snapshots in a historical debugging session. A snapshot gives you a view of your full application state. To enable the capture of snapshots, go to **Tools > Options > IntelliTrace > General**, and select **IntelliTrace snapshots (managed and native)**. For more information, see [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md)
 
 Snapshots are available in Visual Studio Enterprise 2017 version 15.5 and higher, and it requires Windows 10 Anniversary Update or above.  For .NET Core and ASP.NET Core apps, Visual Studio Enterprise 2017 version 15.7 is required. For native apps targeting Windows, Visual Studio Enterprise 2017 version 15.9 Preview 2 is required.
 

docs/debugger/intellitrace.md

@@ -39,7 +39,7 @@ You can use IntelliTrace in Visual Studio Enterprise edition (but not the Profes
 
 |||
 |-|-|
-|**Debug my application with IntelliTrace:**<br /><br /> - Show me past events.<br />- Show me call information with past events.<br />- Save my IntelliTrace session.<br />- Control the data that IntelliTrace collects.|- [View snapshots using IntelliTrace step-back](../debugger/how-to-use-intellitrace-step-back.md)<br />- [Walkthrough: Using IntelliTrace](../debugger/walkthrough-using-intellitrace.md)<br />- [IntelliTrace Features](../debugger/intellitrace-features.md)<br />- [Historical Debugging](../debugger/historical-debugging.md)|
+|**Debug my application with IntelliTrace:**<br /><br /> - Show me past events.<br />- Show me call information with past events.<br />- Save my IntelliTrace session.<br />- Control the data that IntelliTrace collects.|- [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md)<br />- [Walkthrough: Using IntelliTrace](../debugger/walkthrough-using-intellitrace.md)<br />- [IntelliTrace Features](../debugger/intellitrace-features.md)<br />- [Historical Debugging](../debugger/historical-debugging.md)|
 |**Collect IntelliTrace data during a test session in Test Manager**|- [Collect more diagnostic data in manual tests](/azure/devops/test/mtm/collect-more-diagnostic-data-in-manual-tests?view=vsts)|
 |**Collect IntelliTrace data from deployed applications**|- [Using the IntelliTrace stand-alone collector](../debugger/using-the-intellitrace-stand-alone-collector.md)|
 |**Start debugging from an IntelliTrace log file (.iTrace file).**|- [Using saved IntelliTrace data](../debugger/using-saved-intellitrace-data.md)|
@@ -143,7 +143,7 @@ By default, IntelliTrace records only IntelliTrace events: debugger events, exce
 
 You can configure IntelliTrace to capture snapshots at every breakpoint and debugger step event. IntelliTrace records the full application state at each snapshot, which allows you to view complex variables and to evaluate expressions.
 
-See [View snapshots using IntelliTrace step-back](../debugger/how-to-use-intellitrace-step-back.md).
+See [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md).
 
 **Collect function call information**
 

docs/debugger/media/ffr_tfs2017builddefsymbolspath.png

@@ -22,8 +22,8 @@
     href: debug-live-azure-applications.md
   - name: Debug managed and native code
     href: how-to-debug-managed-and-native-code.md
-  - name: View snapshots using IntelliTrace step-back
-    href: how-to-use-intellitrace-step-back.md
+  - name: Inspect previous app states
+    href: view-historical-application-state.md
   - name: Debugging for absolute beginners
     href: debugging-absolute-beginners.md
 - name: How-to guides
@@ -324,7 +324,9 @@
   - name: IntelliTrace
     href: intellitrace.md
     items:
-    - name: "Walkthrough: Using IntelliTrace"
+    - name: View snapshots with IntelliTrace
+      href: view-snapshots-with-intellitrace.md
+    - name: View events with IntelliTrace
       href: walkthrough-using-intellitrace.md
     - name: IntelliTrace features
       href: intellitrace-features.md
@@ -334,10 +336,11 @@
       href: historical-debugging-inspect-app.md
     - name: Diagnose problems after deployment
       href: diagnose-problems-after-deployment.md
-    - name: Using the IntelliTrace stand-alone collector
-      href: using-the-intellitrace-stand-alone-collector.md
-    - name: Using the Microsoft Monitoring Agent
-      href: using-the-microsoft-monitoring-agent.md
+      items:
+      - name: Using the IntelliTrace stand-alone collector
+        href: using-the-intellitrace-stand-alone-collector.md
+      - name: Using the Microsoft Monitoring Agent
+        href: using-the-microsoft-monitoring-agent.md
     - name: Using saved IntelliTrace data
       href: using-saved-intellitrace-data.md
     - name: API Reference for IntelliTrace Extensibility

docs/debugger/media/ffr_tfs2017buildprocesstemplate.png

@@ -1,5 +1,5 @@
 ---
-title: "View a snapshot using IntelliTrace step-back"
+title: "View previous application state using IntelliTrace"
 ms.description: "Learn how to take snapshots, and view snapshots with IntelliTrace step-back"
 ms.custom: "mvc"
 ms.date: "09/19/2018"
@@ -12,7 +12,7 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# View snapshots using IntelliTrace step-back in Visual Studio
+# Inspect previous app states using IntelliTrace step-back in Visual Studio
 
 IntelliTrace step-back automatically takes a snapshot of your application at every breakpoint and debugger step event. The recorded snapshots enable you to go back to previous breakpoints or steps and view the state of the application as it was in the past. IntelliTrace step-back can save you time when you want to see the previous application state but don't want to restart debugging or recreate the desired app state.
 

docs/debugger/media/ffr_tfs2017viewbuilddefinition.png

@@ -0,0 +1,24 @@
+---
+title: "View snapshots with IntelliTrace"
+description: "Use IntelliTrace step-back to examine the historical application state"
+ms.custom: ""
+ms.date: "09/20/2018"
+ms.technology: "vs-ide-debug"
+ms.topic: "quickstart"
+helpviewer_keywords:
+  - "IntelliTrace step-back"
+author: "mikejo5000"
+ms.author: "mikejo"
+manager: douge
+ms.workload:
+  - "multiple"
+---
+# View snapshots with IntelliTrace step-back (Visual Studio Enterprise)
+
+**IntelliTrace step-back** automatically takes a snapshot of your application at every breakpoint and debugger step event. The recorded snapshots enable you to go back to previous breakpoints or steps and view the state of the application as it was in the past. IntelliTrace step-back can save you time when you want to see the previous application state but don't want to restart debugging or recreate the desired app state.
+
+You can navigate and view snapshots by using the **Step Backward** and **Step Forward** buttons in the Debug toolbar. These buttons navigate the events that appear in the **Events** tab in the **Diagnostic Tools** window.
+
+![Step Backward and Forward Buttons](../debugger/media/intellitrace-step-back-icons-description.png  "Step Backward and Forward buttons")
+
+For more information, see [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md).

docs/debugger/toc.yml

@@ -80,5 +80,5 @@ You can use IntelliTrace to collect information about specific events or categor
 
 You can use some of the advanced features of IntelliTrace with historical debugging:
 
- - To view snapshots, see [View snapshots using IntelliTrace step-back](../debugger/how-to-use-intellitrace-step-back.md)
+ - To view snapshots, see [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md)
  - To learn how to inspect variables and navigate code, see [Inspect your app with historical debugging](../debugger/historical-debugging-inspect-app.md)

docs/debugger/how-to-use-intellitrace-step-back.md renamed to docs/debugger/view-historical-application-state.md

@@ -40,7 +40,7 @@ The debugger includes these new features:
 
     ![Step Backward and Forward Buttons](../debugger/media/intellitrace-step-back-icons-description.png  "Step Backward and Forward buttons")
 
-    For more information, see the [View snapshots using IntelliTrace step-back](../debugger/how-to-use-intellitrace-step-back.md) page.
+    For more information, see the [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md) page.
 
 - The **Exception Helper** replaces the Exception Assistant and appears in a non-modal dialog box where the error occurred. The **Exception Helper** provides quicker access to any inner exceptions, additional analysis by the debugger (if available), and immediate access to the **Exception Settings** for the exception. The Exception Helper can also be dragged to a floating view if it is blocking something that you need to see.