Use for isolation deserialization library with generics?

[johanlindfors]

Hey Steve (and the community). I'm trying to leverage the IsolatedRuntime to wrap YamlDotNet in order to demonstrate the possibility of leveraging isolation for code that's out of my scope (as a layer in a secure architecture sample). I'm struggling with wrapping the runtime.Invoke(() => { }); if this is invoked in a method with a generic signature such as the following:

public T Deserialize(string input) {
return runtime.Invoke(() => ... });
}

An exceptions is thrown on the runtime.Invoke as follows:

Unhandled exception. DotNetIsolator.IsolatedException: System.InvalidOperationException: Could not execute the method because the containing type is not fully instantiated.
   at DotNetIsolator.IsolatedRuntime.InvokeDotNetMethod[TRes](Int32 monoMethodPtr, IsolatedObject instance, ReadOnlySpan`1 argAddresses)
   at DotNetIsolator.IsolatedMethod.Invoke[TRes](IsolatedObject instance)
   at DotNetIsolator.IsolatedRuntime.Invoke[TRes](Func`1 value)
   at IsolatedYamlDeserializer.Deserialize[T](String input) in ....

I can successfully call this if called by a non generic method in the same instance. But naturally that doesn't help me in the generic deserialization scenario...