Passing JavaScript argument with ref keyword to .NET Framework DLL

This article provides an introduction to cross-technology invocation of both static and instance methods which contains argument of type ref. Parameter modifier ref in C# (.NET) technology is used in a method signature to pass an argument by reference. It is described in details in this article.

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 methods with ref parameter modifier from .NET Framework 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 Framework 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 static method invocation.

Custom .NET Framework DLL with ref JavaScript argument

With Javonet it is possible to reference any custom .NET Framework 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 Framework DLL which contains methods with ref parameter modifier. 

public static void RefSampleMethod(ref int x)
{
	x = x * 2;
}

public static void RefSampleMethod2(ref int x, ref double y, ref string z)
{
	x = x * 2;
	y = y / 2;
	z = "Done";
}

It is possible to invoke the declared methods from .NET Framework 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().clr()

// set up variables
const libraryPath = resourcesDirectory + "/TestClass.dll"
const className = "TestClass.TestClass"

// load custom library
calledRuntime.loadLibrary(libraryPath)

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

// create values for ref
let refValue1 = calledRuntime.asRef(10).execute()
let intType = calledRuntime.getType("System.Int32").execute()
let refValue2 = calledRuntime.asRef(20.0, intType).execute()

// invoke type's static method with ref values
calledRuntimeType.invokeStaticMethod("RefSampleMethod", refValue1).execute()
calledRuntimeType.invokeStaticMethod("RefSampleMethod", refValue2).execute()

// get ref values
let result1 = refValue1.getRefValue().execute().getValue()
let result2 = refValue2.getRefValue().execute().getValue()

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

This snippet uses in memory runtime bridging to load the .NET Framework DLL and next retrieves reference to specific type.

Next, two reference type arguments are created. An argument that is passed to a ref parameter must be initialized before it's passed to a method. Two ways of initialization are presented in create values for ref section of the snippet.
Fist argument (refValue1) is initialized using asRef() method with default type of passed value (int). This type matches the type of parameter in RefSampleMethod(ref int x) method.
Second argument (refValue2) is initialized using asRef() method with specifying the exact type which should be use. "System.Int32" is an alias for int.

Both values can be passed to RefSampleMethod(ref int x) method using invokeStaticMethod(...).execute() invocation.

Each reference type argument is get as regular JavaScript value using getRefValue() and can be used for further processing.

Custom .NET Framework DLL with multiple ref JavaScript arguments

It is possible to invoke the declared method which contains multiple ref arguments from .NET Framework 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().clr()

// set up variables
const libraryPath = resourcesDirectory + "/TestClass.dll"
const className = "TestClass.TestClass"

// load custom library
calledRuntime.loadLibrary(libraryPath)

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

// create values for ref
let refToInt = calledRuntime.asRef(10).execute()
let refToDouble = calledRuntime.asRef(5, doubleType).execute()
let refToString = calledRuntime.asRef("Before execution").execute()

// invoke type's static method with ref values
calledRuntimeType.invokeStaticMethod("RefSampleMethod2", refToInt, refToDouble, refToString).execute()

// get ref values
let result1 = refToInt.getRefValue().execute().getValue()
let result2 = refToDouble.getRefValue().execute().getValue()
let result3 = refToString.getRefValue().execute().getValue()

// write result to console
console.log(result1)
console.log(result2)
console.log(result3)

This snippet uses in memory runtime bridging to load the .NET Framework DLL and next retrieves reference to specific type.

Next, three reference type arguments are created. An argument that is passed to a ref parameter must be initialized before it's passed to a method. Two ways of initialization are presented in create values for ref section of the snippet.
Fist argument (refToInt) is initialized using asRef() method with default type of passed value (int). This type matches the type of first parameter in RefSampleMethod2 method.
Second value (refToDouble) is initialized using asRef() method with specifying the exact type which should be used. "System.Double" is an alias for double.
Third argument (refToString) is initialized using asRef() method with default type of passed value (string).

All three arguments are processed in RefSampleMethod2 and changed. Their values are obtained using getRefValue() method.

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 Framework 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