James Forshaw

Seems I fixed this issue with querying handles in the latest version of the library, just I haven't updated the version in nuget yet. I really should do that :-)

It's certainly possible that it's a PS related issue. I only tend to test on Windows 10 tbh. Out of interest what is the version of PS on your other...

Odd, looking at it I'd assume it was due to the Attributes property not having the Import flag which might indicate a .NET version issue but you seem to be...

It shouldn't matter too much if you use the output from Windows 10. Though you don't need to use the actctx manifest, you should be able to copy and paste...

Well System.Net.WebClient isn't a registered COM class so it needs the activation manifest to work. But for DotNetToJScript you shouldn't need it. You should be able to get some output...

I appreciate the patch. Is there are advantage to add this to DotNetToJScript versus just using https://github.com/pwntester/ysoserial.net ?

Well, don't do that then ;-) In all seriousness though the tool wasn't really designed with performance in mind, at one point something of that size might have taken 5+...

I could add the DISPID field as that's easily accessible from the converted type library, however the help string is not preserved as far as I can tell. At some...

It's not a problem of getting the information out, it just doesn't match with how I implement the type lib viewing. I convert the type library to a .NET assembly...

Trying to inspect the proxy information isn't an exact science, I have to use a simple heuristic to try and find the data. This means that it doesn't always work....