Share via

WPFPerf Performance Profiling Tools for WPF 4 is now available!

  • Article

The WPFPerf tool comprises of a suite of performance profiling tools that allow you to analyze the run-time behavior of your WPF application and point to potential performance bottlenecks.
We finally release the version that also supports .NET Framework 4 (WPF 4).

This version of the tool (WPFPerf 4) will allow you to profile both WPF 3.5 SP1 and WPF 4 based applications.
The WPFPerf 4 tool is included with the Windows SDK for Windows 7 and .NET Framework 4 (Windows SDK 7.1). So you are welcome to download and send us your feedback.

By the way, the tool itself will run on machines with only .NET 3.5 SP1 or only .NET 4, if both are present it will use .NET 3.5 SP1.
Also, I am not sure how many people had a chance to look at the documentation that is installed with the tool , but we think it is very useful so don't forget to check it out.

Update (6/14/2010):
We heard that few folks complain that the Visual Profiler cannot correctly attach to the WPF application in the new WPFPerf for WPF 4.
After some research we think this has to do with a bug in our DateTime initialization which cause anyone in a time zone > GMT to not get any data in VisualProfiler (for a few hours at least).
Until we post a fix, a temporary workaround is to set your time zone > GMT (e.g.to Eastern or Pacific Standard Time Zones) when you first attach VisualProfiler.

Please try this workaround and let us know.

Update (8/24/2010):
A patch to that fixes the bug in Visual Profiler for certain time zones is now available.
See here.

Comments

  • Anonymous
    May 26, 2010
    For .NET 4 it does not work for me: 'This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.'

  • Anonymous
    May 26, 2010
    For .NET 4 it does not work for me: 'This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.' occurs.

  • Anonymous
    May 28, 2010
    For me also says 'This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded' for a wpf 4.0 application. Also, the Visual Profiler does not do anything when I choose to profile my WPF 4.0 application

  • Anonymous
    May 31, 2010
    the Perforator works for me, but the Visual Profiler can't collect any data while profiling, what's wrong ?

  • Anonymous
    June 01, 2010
    "the Perforator works for me, but the Visual Profiler can't collect any data while profiling, what's wrong ?" I'm having this exact same issue, can't seem to find a solution.

  • Anonymous
    June 03, 2010
    Hi Guys
    We have seen similar reports with the latest WpfPerf tool.
    In some situations simply setting focus on the app or resizing it seems to address the issues w/ Visual Profiler.
    If this did not help, to help us investigate, can you please provide more data. E.g.:
    1.What OS / Service pack are you running ?  Is it 32 or 64 bit OS?
    2.Is your app 32 or 64 bit (e.g. complied  for “x86”, “x64” or “AnyCPU” ?)
    3.Is your app targeting NET4 or 3.5 SP1?
    4.Do you have both .NET 3.5 SP1 and  NET4 installed on your machine?
    5.Is WpfPerf not working when you attach the app ? or launch it from WpfPerf ? (can you please try both)
    6.Are you doing anything unusual in your app (e.g. Hosting 3.5 from your NET4 app, profiling XBAPs)
    7.Is the issue only w/ Visual Profiler or also Perforator ? Thanks in adavnce.
    Jossef

  • Anonymous
    June 06, 2010
    Visual Profiler tool is not working. Even on sample application this tool did not work prefactor is working fine. I am using windows 7 x86 and latest Pref tool for .net 4  and sdk 7.1

  • Anonymous
    June 14, 2010
    We heard that few folks complain that the Visual Profiler cannot correctly attach to the WPF application. After some research we think this has to do with a bug in our  DateTime initialization which cause anyone in a time zone > GMT to not get any data in VisualProfiler (for a few hours at least). Until we post a fix, a temporary workaround is to set your time zone > GMT (e.g.to Eastern or Pacific Standard Time Zones) when you first attach VisualProfiler. Please try this workaround and let us know. Jossef.

  • Anonymous
    June 16, 2010
    The comment has been removed

  • Anonymous
    June 22, 2010
    I'm running version 3.1.0.0 of the PPT for WPF. It works fine for net3 apps but dose not reconize net4 apps. I click Launch Process and select my application and  click Launch. The app starts but the profiler is still waiting for the app to start. I've tried to change the timezone but it dose not fix the problem.

  • Anonymous
    June 22, 2010
    Forgot to mention: When the app is running and I choose to select process the aplication is shown in the list but is grayed out and its not possible to select it.

  • Anonymous
    June 22, 2010
    Found the problem - the 7.1 dose not update the WPF Performance toolkit. I looked through the 7.1 installer log and found the url to the toolkit, downloaded it and installed it. Now it works fine....

  • Anonymous
    June 29, 2010
    Sigurdur, could you share where you found the installer log or the link to the toolkit?   I'm having the same problem and searching for the log...

  • Anonymous
    July 13, 2010
    We had the same problem in Portugal , me , Bruno Sivla and our team, i just found this post again and made the swich on my local time to pacific time and ti works. Thanks. ps - you should release an update.

  • Anonymous
    July 13, 2010
    We had the same problem in Portugal , me , Bruno Sivla and our team, i just found this post again and made the swich on my local time to pacific time and ti works. Thanks. ps - you should release an update.

  • Anonymous
    March 07, 2011
    How do I get the EventTrace enabled?, I have a problem where the WPF app stops responding to the mouse and I think the WpfPerf / Event Trace might be helpful. Unfortunately I only see Perforator and Visual Profiler, and if I try to add EventTrace.dll then I get 'not tools found' Thanks

  • Anonymous
    August 04, 2011
    It looks like this wonderful tool has been abandoned by MSFT :(, isn’t it? How about you, Jossef? Should we use the Visual Studio Profiler instead?