If you run CLR Profiler for .NET 2.0 to analyze the performance of a WPF/.NET 3.0 or .NET 3.5 application you may find that it doesn’t start (i.e. it displays a dialog showing something like "Waiting for application to start the CLR." In this case please make sure:
- you don’t run CLR Profiler 1.1 but 2.0 (this is probably true);
- you don’t run CLR Profiler with standard user rights, i.e. this is by default on Vista; you need to start CLR with administrative rights, and then it will work. As CLR didn’t change with .NET 3.0 nor with .NET 3.5 it works OK with these types of applications.