ANN: Latest version of the WPF Performance Suite now available!
(The following is shamelessly borrowed from: http://blogs.msdn.com/wpfsdk/archive/2007/04/26/latest-version-of-wpfperf-exe-available.aspx)
Latest version of WPFPerf.exe available
The latest version of the WPF Performance Suite has just be released in the Windows SDK for Windows Server and .NET Framework 3.5! If you install the SDK, you'll find WpfPerf.msi, which lets you install the latest perf suite. The accompanying “Performance Profiling Tools for WPF” article has been updated to reflect the changes, but note that the MSDN version of the doc still reflects the previous version of the tool.
In addition to UI enhancements for usability, this version of the performance suite includes fixes to all previously known crashes. Please remember to remove all older versions of WPFPerf.exe before installing this version of the performance suite!
All Replies
- Does this include an x64 build?
Do I also need to install .Net 3.5 runtimes and Native Orcas beta 1?
I have a .Net 3.0 production PC and I am not sure that I want to remove the .Net 3.0 SDK and put the .Net 3.5 SDK on.
Is there any way to just upgrade the performance suite?
Steve
- I second that. It would be nice to be able to download a standalone installer, and I'm crossing my fingers for x64 support.
- Imad There actually is a standalone installer available - for both x86 and x64, and both should be included in the linked SDK img. The performance tools have no 3.5 requirements, and should happily install and run against RTM 3.0 bits. We're working on finding a better, more convenient way of distributing the installer, but until then you'll find it as part of the above SDK.
- Ok, I downloaded the SDK, extracted the files using MagicISO, and looked around for wpfperf.msi. I found it in the following file (I'm looking for the x64 version):
WinSDKNetFxTools-WinSDKNetFxTools-amd64.0.cab
So I extract with winrar, rename wpfperf_msi.5F337A86_D732_4474_800D_C45B59A05224 to wpfperf.msi, and install. The install goes fine. I'm smiling. For a few seconds...
None of the performance tools seem to be able to find running WPF processes, whether XBAPs or standalone executables... Any ideas what's going on? Does the wpfperf.msi package have some dependency on another package from the SDK?
- Imad I'm also on x64. I can see x64 processes but I can't see any x86 processes.
I'm trying to use the "Visual Profiler" in WPF Perf. Trying to attach to an existing x64 process crashes WPF Perf.
Launching a new process loads the application but WPF Perf continues to say "Please wait while the application is being launched..."
If I try to launch an x86 assembly (some of my apps have dependencies on SQL CE and Ink Analysis) I get the error message "Unable to connect to target application. Profiling will now be stopped."
You could try copying WpfPerformanceDiagnostics.dll into the directory with the application that you are going to profile. This file is included in the wpfperf.msi, which installs by default to C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin. Once you run the MSI, you will find the file in c:\Windows\assembly\GAC_32\WpfPerformanceDiagnostics.
K a r i n M e i e r
Windows SDK | Samples & Community PM
We installed the WPF Performance suite on a 32 bit and 64 bit machine. After moving the WpfPerformanceDiagnostics.dll to the application directory, we were able to get the Performance suite working on the 32 bit machine. However on the 64 bit machine we cannot ever see our appliations, or any application processes.


