Pass arguments by reference with out keyword to .NET DLL in JavaScript app

This article provides an introduction to cross-technology invocation of both static and instance methods which contains argument of type out. Parameter modifier out 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 out parameter modifier 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 JavaScript with out keyword

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 methods with out parameter modifier. 

public static void OutSampleMethod(out string outStr)
{
    outStr = "String from OutSampleMethod";
}

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
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 stringType = calledRuntime.getType("System.String").execute()

// create values for outs
let outValue1 = calledRuntime.asOut(stringType).execute()
let outValue2 = calledRuntime.asOut('c', stringType).execute()
let outValue3 = calledRuntime.asOut("Test string").execute()

// invoke type's static method with out values
calledRuntimeType.invokeStaticMethod("OutSampleMethod", outValue1).execute()
calledRuntimeType.invokeStaticMethod("OutSampleMethod", outValue2).execute()
calledRuntimeType.invokeStaticMethod("OutSampleMethod", outValue3).execute()

// get outs' values
let result1 = outValue1.getRefValue().execute().getValue()
let result2 = outValue2.getRefValue().execute().getValue()
let result3 = outValue3.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 DLL and next retrieves reference to specific type.
Next, two reference type arguments are created. An argument that is passed to a out parameter do not have to be initialized before it's passed to a method. Three ways of initialization are presented in create values for out section of the snippet.
Fist way (outValue1) is initializing using asOut() method with specifying type of argument.
Second way (outValue2) is initializing using asOut() method with specifying value and type of argument.
Third way (outValue3) is initializing using asOut() method with specifying value of argument.

All these values can be passed to OutSampleMethod(out string outStr) method using invokeStaticMethod(...).execute() invocation.

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

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