Collect concurrency data for stand-alone applications by using the profiler command line
Applies to: 
Visual Studio 
Visual Studio for Mac
Note
This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
The concurrency method of Visual Studio Profiling Tools enables you to collect resource contention data and thread activity data that shows you CPU utilization, thread contention, thread migration, synchronization delays, areas of overlapped IO, and other system events.
Common tasks
| Task | Related content |
|---|---|
| Start a .NET Framework application and profile concurrency data | - How to: Launch a .NET Framework application to collect concurrency data |
| Start a C/C++ application and profile concurrency data | - How to: Launch a native application to collect concurrency data |
| Attach the profiler to a running .NET Framework application | - How to: Attach the profiler to a .NET Framework application to collect concurrency data |
| Attach the profiler to a running C/C++ application | - How to: Attach the profiler to a native application and collect concurrency data |
Related tasks
Profile stand-alone applications
| Task | Related content |
|---|---|
| Profile by using the sampling method | - Collect application statistics using sampling |
| Profile by using the instrumentation method | - Collect detailed timing data using instrumentation |
| Profile .NET memory allocation and garbage collection | - Collect .NET Framework memory data |
| Add tier-interaction data | - Collect tier interaction data |
Profile concurrency issues
| Task | Related content |
|---|---|
| Profile ASP.NET applications | - Collect concurrency data |
| Profile services | - Collect concurrency data |