Hi,
This is actually a bug :(
It happens when you pass null as a value to the invoked method.
We will fixed it and I'll update you as soon as it is fixed.
Please note that even after the fix there might be some restrictions on invoking private methods with overloads.
Consider the example:
public class SomeArgType1
{}
public class SomeArgType2
{}
public class Foo
{
private void Bar(SomeArgType1 arg)
{}
private void Bar(SomeArgType2 arg)
{}
}
// test code
Foo foo = new Foo();
Isolate.Invoke.Method(foo, "Bar", null)
In the example above Isolator will not be able to decide which overload of Bar you want to call unless you'll send a non null instance as an argument.
