"View Proxy Definition" throws NullReferenceException on Windows 11 22H2 about oleviewdotnet HOT 3 OPEN

Sorry that I didn't reply for so long. It does seem that MS is no longer building proxy definitions with names anymore which is a real shame as that was super helpful. I've added a fix for the NPD so hopefully it at least doesn't crash.

from oleviewdotnet.

I also got it running by simply making it name ?? "" in my fork:

https://github.com/Ciantic/oleviewdotnet/blob/e3306cbab9fd05c6951adce320e80cb20977aee8/OleViewDotNet.Main/COMUtilities.cs#L2039

However this is not a fix yet, where can we get more WinRT names? Now they are all null or empty, it's still better but we need to figure out a way to get mangled names.

from oleviewdotnet.

@tyranid There are tools such as https://github.com/t1m0thyj/GetVirtualDesktopAPI_DIA that gets the PDB symbols from Micorosoft.com/symbols and combines them to produce proxy definition interface with all the names. Even for Windows internals such as those Virtual Desktop APIs.

I know that oleviewdotnet is probably on maintenance, but that's what I was actually looking to do with my fork, somehow download symbols and combine.

Here is an example I produced with that python script:

https://github.com/Ciantic/DumpVDIA/blob/master/current.txt

I think the combination needs to find an implementing class from a DLL, and with PDB figure out the interface definitions from there. It's kind of tricky.

EDIT Now I know, it should be separate feature, to browse class instances that can be viewed with PDB, that's how IDA does it too, but it's view is so confusing compared to oleview

from oleviewdotnet.