WPF Performance Suite not working anymore with WPF / .NET 8

[electro-logic]

Description

Actions / Select Process can't list WPF / .NET 8 processes

Reproduction Steps

1. Install WPF Performance Suite from https://learn.microsoft.com/it-it/archive/blogs/kirillosenkov/where-to-download-wpf-performance-suite-perforator-visual-profiler
2. Run WPF Performance Suite
3. Click on Actions / Select Process

Expected behavior

WPF apps is shown

Actual behavior

WPF apps are not shown

Regression?

.Net Framework is working

Known Workarounds

No response

Impact

Can't profile performance of WPF apps

Configuration

No response

Other information

No response

[thejonathanbrown]

+1 same issue. That build of the performance suite looks quite old. Is that tool still maintained and is there a newer version?

[electro-logic]

+1 same issue. That build of the performance suite looks quite old. Is that tool still maintained and is there a newer version?

Would be great to have a "revamped" performance tool in future

[CycloneRing]

Did you installed https://download.microsoft.com/download/1/8/9/189A7832-49D8-4978-85E8-3DFFF44E6C04/WpfPerf_timezone_patch.msp ?

[electro-logic]

I don't remember, but link is broken, can you attach the patch? Thank you

[mo-russo]

I'm able to launch a .NET8 WPF application in Perforator (we're generating a .exe for our .NET8 application and not using "dotnet.exe" to start it) but like you, I can't attach to the process once the application is running. I wish MS would open source this application, I would take a look to make a fix for the attach to process.

[boriskv]

you can find the patch in the legacy update archive: https://legacyupdate.net/download-center/download/21042/wpf-performance-suite-patch If you can't attach in the Perforator tool, make sure you start Performance Tool first, then your app, then try attaching.

I agree though, if they made this tool open source it would've been much easier to address issues and add improvements, but I doubt they will do it as they've integrated some of functionality into Visual Studio but I find it a bit more clunky/less convenient for some use cases.