Create Ruby instance and call instance method from .NET Framework DLL
This article provides an introduction to cross-technology creation of instances of classes and invocation of instance methods.
With Javonet you can interact with classes from .NET Framework DLL like they were available in Ruby but invocation must be performed through Javonet SDK API, passing type and method name as string.
Javonet allows you to pass any Ruby value type as argument to instance method from .NET Framework DLL. In example: int, float, string, char, long and other. 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.
Using Ruby in custom .NET Framework DLL
With Javonet it is possible to reference any custom .NET Framework DLL and interact with public methods declared on types defined within that module almost the same as with any other Ruby library.
This section present sample custom .NET Framework DLL with class declaring methods and Javonet SDK syntax required to create object and invoke that methods and consume the results in Ruby.
Snippet below represents the sample code from .NET Framework DLL which contains class and its methods:
public static int MultiplyByTwo(int a)
{
return 2 * a;
}
public int MultiplyTwoNumbers(int a, int b)
{
return a * b;
}
It is possible to invoke one of the declared instance methods from .NET Framework DLL using following Ruby code.
# use activate only once in your app
Javonet.activate('your-license-key')
# create called runtime context
called_runtime = Javonet.in_memory.clr
# set up variables
library_path = "#{resources_directory}/TestClass.dll"
class_name = 'TestClass.TestClass'
# load custom library
called_runtime.load_library(library_path)
# get type from the runtime
called_runtime_type = called_runtime.get_type(class_name).execute
# create type's instance
instance = called_runtime_type.create_instance.execute
# invoke instance's method
response = instance.invoke_instance_method('MultiplyTwoNumbers', 5, 4).execute
# get value from response
result = response.get_value
# write result to console
puts result
In code snippet above you can see how easily you can activate Javonet and instruct it using inMemory() method to create new RuntimeContext that will run netframework-dll runtime within your current process. Next with addLibrary method it triggers the load of required netframework-dll module and allows you to interact with any classes and their methods defined in that package.
Further call to createInstance() allows to create instance of class. Calls to invokeInstanceMethod() allows to call "multiplyTwoNumbers" netframework-dll instance method and pass the value type arguments. With Javonet you can invoke methods with any number and any type of arguments including value type arguments, reference type arguments, arrays and collections.
You can receive and further process and type of result returned by called netframework-dll method, regardless if it is reference type that will get returned as another instance of Invocation Context that you can use for further interaction, or value type that you can obtain as ruby value with getValue() method.
Using Ruby framework .NET Framework DLL
The same steps are required to use types and methods from standard .NET Framework DLL:
# use activate only once in your app
Javonet.activate('your-license-key')
# create called runtime context
called_runtime = Javonet.in_memory.clr
# get type from the runtime
called_runtime_type = called_runtime.get_type('System.DateTime').execute
# create type's instance
instance = called_runtime_type.create_instance(2022, 9, 1).execute
# call instance's method
response = instance.invoke_instance_method('ToShortDateString').execute
# get value from response
result = response.get_value
# write result to console
puts result
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.
Was this article helpful?