Skip to content

Commit a6f4860

Browse files
changeworldchangeworld
authored
Delete unnecessary spaces
1 parent 29cc80d commit a6f4860

File tree

1 file changed

+62
-62
lines changed

1 file changed

+62
-62
lines changed

‎docs/debugger/walkthrough-using-intellitrace.md

Lines changed: 62 additions & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -6,79 +6,79 @@ ms.assetid: e1c9c91a-0009-4c4e-9b4f-c9ab3a6022a7
66
author: "mikejo5000"
77
ms.author: "mikejo"
88
manager: jillfra
9-
ms.workload:
9+
ms.workload:
1010
- "multiple"
1111
---
1212
# View events with IntelliTrace in Visual Studio Enterprise (C#, Visual Basic)
1313

14-
You can use IntelliTrace to collect information about specific events or categories of events, or about individual function calls in addition to events. The following procedures show how to do this.
15-
16-
You can use IntelliTrace in Visual Studio Enterprise edition, but not the Professional or Community editions.
17-
18-
## <a name="GettingStarted"></a> Configure IntelliTrace
14+
You can use IntelliTrace to collect information about specific events or categories of events, or about individual function calls in addition to events. The following procedures show how to do this.
1915

20-
You can try debugging with just IntelliTrace events. IntelliTrace events are debugger events, exceptions, .NET Framework events, and other system events. You should turn on or turn off specific events to control the events that IntelliTrace records before you start debugging. For more information, see [IntelliTrace Features](../debugger/intellitrace-features.md).
21-
22-
- Turn on the IntelliTrace event for File Access. Go to the **Tools > Options > IntelliTrace > IntelliTrace Events** page, and expand the **File** category. Check the **File** event category. This causes all the file events (access, close, delete) to be checked.
16+
You can use IntelliTrace in Visual Studio Enterprise edition, but not the Professional or Community editions.
17+
18+
## <a name="GettingStarted"></a> Configure IntelliTrace
19+
20+
You can try debugging with just IntelliTrace events. IntelliTrace events are debugger events, exceptions, .NET Framework events, and other system events. You should turn on or turn off specific events to control the events that IntelliTrace records before you start debugging. For more information, see [IntelliTrace Features](../debugger/intellitrace-features.md).
21+
22+
- Turn on the IntelliTrace event for File Access. Go to the **Tools > Options > IntelliTrace > IntelliTrace Events** page, and expand the **File** category. Check the **File** event category. This causes all the file events (access, close, delete) to be checked.
2323

2424
## Create your app
25-
26-
1. Create a C# console application. In the Program.cs file, add the following `using` statement:
27-
28-
```csharp
29-
using System.IO;
30-
```
31-
32-
2. Create a <xref:System.IO.FileStream> in the Main method, read from it, close it, and delete the file. Add another line just to have a place to set a breakpoint:
33-
34-
```csharp
35-
static void Main(string[] args)
36-
{
37-
FileStream fs = File.Create("WordSearchInputs.txt");
38-
fs.ReadByte();
39-
fs.Close();
40-
File.Delete("WordSearchInputs.txt");
41-
42-
Console.WriteLine("done");
43-
}
44-
```
45-
46-
3. Set a breakpoint on `Console.WriteLine("done");`
25+
26+
1. Create a C# console application. In the Program.cs file, add the following `using` statement:
27+
28+
```csharp
29+
using System.IO;
30+
```
31+
32+
2. Create a <xref:System.IO.FileStream> in the Main method, read from it, close it, and delete the file. Add another line just to have a place to set a breakpoint:
33+
34+
```csharp
35+
static void Main(string[] args)
36+
{
37+
FileStream fs = File.Create("WordSearchInputs.txt");
38+
fs.ReadByte();
39+
fs.Close();
40+
File.Delete("WordSearchInputs.txt");
41+
42+
Console.WriteLine("done");
43+
}
44+
```
45+
46+
3. Set a breakpoint on `Console.WriteLine("done");`
4747

4848
## Start debugging and view IntelliTrace events
49-
50-
1. Start debugging as usual. (Press **F5** or click **Debug > Start Debugging**.
51-
49+
50+
1. Start debugging as usual. (Press **F5** or click **Debug > Start Debugging**.
51+
5252
> [!TIP]
53-
> Keep the **Locals** and **Autos** windows open while you're debugging to see and record the values in those windows.
54-
55-
2. Execution stops at the breakpoint. If you do not see the **Diagnostic Tools** window, click **Debug > Windows > IntelliTrace Events**.
56-
57-
In the **Diagnostic Tools** window, find the **Events** tab (You should see 3 tabs, **Events**, **Memory Usage**, and **CPU Usage**). The **Events** tab shows a chronological list of events, ending with the last event before the debugger broke execution. You should see an event named **Access WordSearchInputs.txt**.
58-
59-
The following screenshot is from Visual Studio 2015 Update 1.
60-
61-
![IntelliTrace&#45;Update1](../debugger/media/intellitrace-update1.png "IntelliTrace-Update1")
62-
63-
3. Select the event to expand its details.
64-
65-
The following screenshot is from Visual Studio 2015 Update 1.
66-
67-
![IntelliTraceUpdate1&#45;SingleEvent](../debugger/media/intellitraceupdate1-singleevent.png "IntelliTraceUpdate1-SingleEvent")
68-
69-
You can choose the pathname link to open the file. If the full pathname is not available, the **Open File** dialog box appears.
70-
71-
Click **Activate Historical Debugging**, which sets the debugger's context to the time when the selected event was collected, showing historical data in the **Call Stack**, **Locals** and the other participating debugger windows. If source code is available, Visual Studio moves the pointer to the corresponding code in the source window so you can examine it.
72-
73-
The following screenshot is from Visual Studio 2015 Update 1.
74-
75-
![HistoricalDebugging&#45;Update1](../debugger/media/historicaldebugging-update1.png "HistoricalDebugging-Update1")
76-
77-
4. 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.
78-
53+
> Keep the **Locals** and **Autos** windows open while you're debugging to see and record the values in those windows.
54+
55+
2. Execution stops at the breakpoint. If you do not see the **Diagnostic Tools** window, click **Debug > Windows > IntelliTrace Events**.
56+
57+
In the **Diagnostic Tools** window, find the **Events** tab (You should see 3 tabs, **Events**, **Memory Usage**, and **CPU Usage**). The **Events** tab shows a chronological list of events, ending with the last event before the debugger broke execution. You should see an event named **Access WordSearchInputs.txt**.
58+
59+
The following screenshot is from Visual Studio 2015 Update 1.
60+
61+
![IntelliTrace&#45;Update1](../debugger/media/intellitrace-update1.png "IntelliTrace-Update1")
62+
63+
3. Select the event to expand its details.
64+
65+
The following screenshot is from Visual Studio 2015 Update 1.
66+
67+
![IntelliTraceUpdate1&#45;SingleEvent](../debugger/media/intellitraceupdate1-singleevent.png "IntelliTraceUpdate1-SingleEvent")
68+
69+
You can choose the pathname link to open the file. If the full pathname is not available, the **Open File** dialog box appears.
70+
71+
Click **Activate Historical Debugging**, which sets the debugger's context to the time when the selected event was collected, showing historical data in the **Call Stack**, **Locals** and the other participating debugger windows. If source code is available, Visual Studio moves the pointer to the corresponding code in the source window so you can examine it.
72+
73+
The following screenshot is from Visual Studio 2015 Update 1.
74+
75+
![HistoricalDebugging&#45;Update1](../debugger/media/historicaldebugging-update1.png "HistoricalDebugging-Update1")
76+
77+
4. 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.
78+
7979
## Next Steps
8080

8181
You can use some of the advanced features of IntelliTrace with historical debugging:
8282

83-
- To view snapshots, see [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md)
84-
- To learn how to inspect variables and navigate code, see [Inspect your app with historical debugging](../debugger/historical-debugging-inspect-app.md)
83+
- To view snapshots, see [Inspect previous app states using IntelliTrace](../debugger/view-historical-application-state.md)
84+
- To learn how to inspect variables and navigate code, see [Inspect your app with historical debugging](../debugger/historical-debugging-inspect-app.md)

0 commit comments

Comments
 (0)