Skip to content

Delete unnecessary spaces #2458

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 12, 2019
Merged

Delete unnecessary spaces #2458

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
124 changes: 62 additions & 62 deletions docs/debugger/walkthrough-using-intellitrace.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,79 +6,79 @@ ms.assetid: e1c9c91a-0009-4c4e-9b4f-c9ab3a6022a7
author: "mikejo5000"
ms.author: "mikejo"
manager: jillfra
ms.workload:
ms.workload:
- "multiple"
---
# View events with IntelliTrace in Visual Studio Enterprise (C#, Visual Basic)

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.

You can use IntelliTrace in Visual Studio Enterprise edition, but not the Professional or Community editions.

## <a name="GettingStarted"></a> Configure IntelliTrace
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.

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).

- 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.
You can use IntelliTrace in Visual Studio Enterprise edition, but not the Professional or Community editions.

## <a name="GettingStarted"></a> Configure IntelliTrace

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).

- 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.

## Create your app
1. Create a C# console application. In the Program.cs file, add the following `using` statement:
```csharp
using System.IO;
```
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:
```csharp
static void Main(string[] args)
{
FileStream fs = File.Create("WordSearchInputs.txt");
fs.ReadByte();
fs.Close();
File.Delete("WordSearchInputs.txt");
Console.WriteLine("done");
}
```
3. Set a breakpoint on `Console.WriteLine("done");`

1. Create a C# console application. In the Program.cs file, add the following `using` statement:

```csharp
using System.IO;
```

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:

```csharp
static void Main(string[] args)
{
FileStream fs = File.Create("WordSearchInputs.txt");
fs.ReadByte();
fs.Close();
File.Delete("WordSearchInputs.txt");

Console.WriteLine("done");
}
```

3. Set a breakpoint on `Console.WriteLine("done");`

## Start debugging and view IntelliTrace events
1. Start debugging as usual. (Press **F5** or click **Debug > Start Debugging**.

1. Start debugging as usual. (Press **F5** or click **Debug > Start Debugging**.

> [!TIP]
> Keep the **Locals** and **Autos** windows open while you're debugging to see and record the values in those windows.
2. Execution stops at the breakpoint. If you do not see the **Diagnostic Tools** window, click **Debug > Windows > IntelliTrace Events**.
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**.
The following screenshot is from Visual Studio 2015 Update 1.
![IntelliTrace&#45;Update1](../debugger/media/intellitrace-update1.png "IntelliTrace-Update1")
3. Select the event to expand its details.
The following screenshot is from Visual Studio 2015 Update 1.
![IntelliTraceUpdate1&#45;SingleEvent](../debugger/media/intellitraceupdate1-singleevent.png "IntelliTraceUpdate1-SingleEvent")
You can choose the pathname link to open the file. If the full pathname is not available, the **Open File** dialog box appears.
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.
The following screenshot is from Visual Studio 2015 Update 1.
![HistoricalDebugging&#45;Update1](../debugger/media/historicaldebugging-update1.png "HistoricalDebugging-Update1")
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.
> Keep the **Locals** and **Autos** windows open while you're debugging to see and record the values in those windows.

2. Execution stops at the breakpoint. If you do not see the **Diagnostic Tools** window, click **Debug > Windows > IntelliTrace Events**.

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**.

The following screenshot is from Visual Studio 2015 Update 1.

![IntelliTrace&#45;Update1](../debugger/media/intellitrace-update1.png "IntelliTrace-Update1")

3. Select the event to expand its details.

The following screenshot is from Visual Studio 2015 Update 1.

![IntelliTraceUpdate1&#45;SingleEvent](../debugger/media/intellitraceupdate1-singleevent.png "IntelliTraceUpdate1-SingleEvent")

You can choose the pathname link to open the file. If the full pathname is not available, the **Open File** dialog box appears.

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.

The following screenshot is from Visual Studio 2015 Update 1.

![HistoricalDebugging&#45;Update1](../debugger/media/historicaldebugging-update1.png "HistoricalDebugging-Update1")

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.

## Next Steps

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

- 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)
- 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)