C# Test Explorer & Debug runner
Overview
Running and Debugging .NET Core Applications
To run and debug your .NET Core applications, you can use the built-in .NET Core Debugger. You can start debugging by pressing F5 and select the .NET Core Debugger configuration. You can also create a launch.json file with the following content:
{
"version": "0.2.0",
"configurations": [
{
"name": ".NET Core Debugger (launch)",
"type": "coreclr",
"request": "launch",
"program": "${command:dotrush.activeTargetPath}",
"preLaunchTask": "dotrush: Build"
},
{
"name": ".NET Core Debugger (attach)",
"type": "coreclr",
"request": "attach",
"processId": "${command:dotrush.pickProcess}"
}
]
}
You can change the startup project by clicking on it and executing the Set as Startup Project command from the context menu. You can also change the debugger options in the VSCode settings.
Running and Debugging NUnit / xUnit / MSTest Tests
To run and debug your VSTest tests, you can use the integrated Test Explorer in VSCode. Run test by clicking on the run button next to the test or debug it by right-clicking on the run button and selecting the Debug Test option in the context menu.
You can change the debugger options in the VSCode settings.
- For the
trace report, you can use the Speedscope in VSCode extension to view it. Alternatively, you can upload it directly to the speedscope site.
- For the
gcdump report, you can use the dotnet-heapview or Visual Studio for Windows.
