Visual Studio 2012 and Debugger .NATVIS files – what can I do with them?

In Visual Studio 2012 , Visual Studio native debugger introduces a new type visualization framework that allows customizing the way Visual Studio displays native types in debugger variable windows (watch, locals, data tips etc.). It supersedes the autoexp.dat file that has been used in earlier versions of Visual Studio and offers xml syntax, better diagnostics,…

7

“Performance reports must be created on a local drive”

For better performance, VS Profiler requires the report to be on a local drive. If you change the report file location through Performance Session properties page (right click on performance session in Performance Explorer –> Properties –> General): then you end up with an error like that: The rationale behind usage of local drives is…

1

VS2010 SP1: Silverlight 4 profiling from Visual Studio UI

  If you install recently published VS2010 SP1 Beta, you can discover that VS Profiler team enriched Silverlight profiling user experience. Previously I published few posts about VS2010 usage for those purposes, either through VS Profiler command line tools or VS2010 UI. Both approaches led you to the final results or figuring out the bottlenecks…

3

CPU Performance Counters in Visual Studio 2010 Profiler

  While using Visual Studio Profiler either from Visual Studio UI or through command line tools, you may wish to collect more/different information using specific CPU Performance Counters. The collected data depends on the profiling mode. As usage of CPU Performance Counters considered an advanced technique, let me explain what is the proper way to…

2

Thread Performance: Resource Contention Concurrency Profiling in Visual Studio 2010

Does your native code deals with critical sections or other synchronization primitives? Does your managed code uses C# lock statement or Monitor class? If yes, and if you would like to get a clear picture of all contentions in your application, you might want to check out the new profiling mode of VS2010 Profiler –…

0

VS2010: Silverlight 4 profiling from Visual Studio UI

In my previous post I showed how VS2010 Profiler command line tools can be used to profile your Silverlight 4 application, as this feature is only partially integrated with Visual Studio UI. While we are working on a full integration story, let me show you how VS UI can be used (with some extra work)…

3

VS2010: Silverlight 4 profiling

Did you know that Visual Studio 2010 Profiler allows you to profile your Silverlight 4 applications? You didn’t? It does. This feature, however, is only partially integrated with Visual Studio UI, and you need to use command line tools to collect the data. After that, you can open the resulting .VSP file in Visual Studio…

30

Resource Contention Concurrency Profiling in Visual Studio 2010 – Performance Investigation Flows

Visual Studio 2010 brings a number of innovations to multithreaded and parallel computing. One of them is Resource Contention Concurrency Profiling. John Robbins gives a really great first look at this feature in his Wintellect VS 2010 Beta 2 Concurrency Resource Profiling In Depth First Look post. The June 2010 issue of MSDN magazine contains…

0

VS2010: Using profiler to improve cache data locality

A recent Concurrency Hazards: False Sharing article demonstrates how VS2010 profiler can be used to detect source of cache data locality issues. To achieve this, you can sample with cache specific CPU performance counters, as long as you do not run inside Virtual Machine or on Hyper-V enabled environment (and this is why). In post-VS2010…

0

PRF0025: No data was collected – why is that?

One day, you may try to use Visual Studio profiler to sample an application you develop, and end up with an error saying no data is collected: Profiling started.Profiling process ID 2752 (<Your Application Name>).Process ID 2752 has exited.Data written to C:\<some path>\Report100114.vsp.Profiling finished.PRF0025: No data was collected. Profiling complete. There could be number of…

0