Collecting .NET Framework Memory Data for Stand-Alone Applications by Using the Profiler Command Line
Note
This article applies to Visual Studio 2015. 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
This section describes the procedures and options for collecting memory allocation and object lifetime data for a .NET client (stand-alone) application by using the sampling method from the command line.
Common Tasks
| Task | Related content |
|---|---|
| Start an application and profile .NET memory | - How to: Launch a .NET Framework Application with the Profiler to Collect Memory Data |
| Attach the profiler to a .NET application | - How to: Attach the Profiler to a .NET Framework Application to Collect Memory Data |
| Instrument an application to collect .NET memory data | - How to: Instrument a Stand-Alone .NET Framework Component and Collect Memory Data with the Profiler |
Related Tasks
Profiling Stand-Alone Applications
| Task | Related content |
|---|---|
| Profile by using the sampling method | - Collecting Application Statistics Using Sampling |
| Profile by using the instrumentation method | - Collecting Detailed Timing Data Using Instrumentation |
| Profile resource contention and thread activity | - Collecting Concurrency Data |
| Adding tier-interaction data | - Collecting tier interaction data |
Profiling .NET Memory Data
| Task | Related content |
|---|---|
| Profiling ASP.NET applications | - Collecting Memory Data |
| Profiling services | - Collecting .NET Memory Data |