Call .NET DLL generic instance method in .NET DLL app

This article provides an introduction to cross-technology invocation of instance generic methods. Generic methods in C# (.NET) and Java technologies are methods that are declared with the type parameter in its signature, allowing it to be used with any data type. It is described in detail in article about generic methods in .NET and article about generic methods in Java.

Javonet allows you to reference and use modules or packages written in (Java/Kotlin/Groovy/Clojure, C#/VB.NET, Ruby, Perl, Python, JavaScript/TypeScript) like they were created in your technology. If have not yet created your first project check Javonet overview and quick start guides for your technology.

With Javonet you can interact with generic instance methods from .NET DLL like they were available in JavaScript but invocation must be performed through Javonet SDK API.

Javonet allows you to pass any JavaScript value type as argument to method from .NET DLL. For reference type arguments (instances of other classes) you can create such instance with Javonet and pass the Invocation Context variable referencing that object as argument of method invocation.

Custom .NET DLL with generic methods

With Javonet it is possible to reference any custom .NET DLL and interact with its methods declared on types defined within that module almost the same as with any other JavaScript library.

Snippet below represents the sample code from .NET DLL which contains generic methods.

public static string GenericSampleStaticMethod<T>(T x, T y)
{
	return x + " and " + y;
}

public string GenericSampleMethod<T>(T x, T y)
{
	return x + " or " + y;
}

public K GenericSampleMethodWithTwoTypes<T, K>(T x)
{
	return default(K);
}

It is possible to invoke the declared methods from .NET DLL using following JavaScript code:

I code in:
// use Activate only once in your app
Javonet.activate("your-license-key")

// create called runtime context
let calledRuntime = Javonet.inMemory().netcore()

// set up variables
let libraryPath = resourcesDirectory + '/TestClass.dll'
let className = 'TestClass.TestClass'

// load custom library
calledRuntime.loadLibrary(libraryPath)

// get type from the runtime
let calledRuntimeType = calledRuntime.getType(className).execute()

// create type's instance
let instance = calledRuntimeType.createInstance().execute()

// get type for generic method
let targetType = calledRuntime.getType("System.Int32")

// invoke type's method
let response = instance.invokeGenericMethod("GenericSampleMethod", targetType, 7, 5).execute()

// get value from response
let result = response.getValue()

// write result to console
console.log(result)

This snippet uses in memory runtime bridging to load the .NET DLL.
Next, type is specified and instance of class is created.
Next, generic instance method is invoked.
While calling .NET generic method it is necessary to pass method name, type and arguments.
While calling Java generic method it is necessary to pass method name and arguments.

To invoke method which has more than one type specified:

I code in:
// use Activate only once in your app
Javonet.activate("your-license-key")

// create called runtime context
let calledRuntime = Javonet.inMemory().netcore()

// set up variables
let libraryPath = resourcesDirectory + '/TestClass.dll'
let className = 'TestClass.TestClass'

// load custom library
calledRuntime.loadLibrary(libraryPath)

// get type from the runtime
let calledRuntimeType = calledRuntime.getType(className).execute()

// create type's instance
let instance = calledRuntimeType.createInstance().execute()

// get types for generic method
let targetType1 = calledRuntime.getType("System.String")
let targetType2 = calledRuntime.getType("System.Int32")

// invoke type's method
let response = instance.invokeGenericMethod("GenericSampleMethodWithTwoTypes",
    [targetType1, targetType2], "test").execute()

// get value from response
let result = response.getValue()

// write result to console
console.log(result)

This snippet uses in memory runtime bridging to load the .NET DLL.
Next, type is specified and instance of class is created.
Next, generic instance method is invoked.
While calling .NET generic method it is necessary to pass method name, type and arguments.
While calling Java generic method it is necessary to pass method name and arguments.
The same operation can be performed remotely by just changing the new Runtime Context invocation from in memory to tcp that will create and interact with your .NET DLL objects on any remote node, container or service that hosts Javonet Code Gateway. This way you can preserve the same logic in your application and instantly switch between monolithic and microservices architecture without the need to implement the integration layer based on web services or other remote invocation methods.

Read more about use cases and software architecture scenarios where Javonet runtime bridging technology can support your development process.

Additional references