Null Reference Exception when Replacing ShowDialog() on a WinForm about pose HOT 6 OPEN

Hey @johnkoerner. Thanks for reporting these issues. Most of these problems is as a result of incorrect MSIL generated during the rewriting of a method. I'm currently working on an under the hood re-implementation of Pose that replaces IL generation with Expression Trees which should fix most of the issues with Pose as well as open up more features like breakpoint support etc.

This re-implementation should be rolling out in about a week or two, but in the meantime I'll take a look at fixing this issue.

from pose.

@tonerdo we, as a community, are looking forward to see the new implementation! If you need any help, feel free to ask.

from pose.

Thanks for the update @tonerdo . When you feel it is ready, let me know and I can pull a branch and build it to test it out.

from pose.

This may be related to #11 as the stack traces are similar.

from pose.

Any update on the new implementation? I am getting this same exception when trying to use Pose in conjunction with Moq.

from pose.

I believe I'm experiencing this exception too. For me, changing the last line of GetRuntimeMethodForVirtual, in StubHelper.cs, to

return type.GetMethod(methodInfo.Name, bindingFlags, null, types, null) ??
    type.GetMethod($"{methodInfo.DeclaringType.FullName}.{methodInfo.Name}", BindingFlags.Instance | BindingFlags.NonPublic, null, types, null);

did the trick.

My analysis is that, without this change, GetRuntimeMethodForVirtual does not know how to handle explicit interface implementations.

VB.NET's Implements keyword may cause similar problems; I've never checked out what they look like under the hood.

from pose.