Working with Ruby collections from .NET Framework DLL

This article provides an introduction to cross-technology handling of collections. Data structures are one of the essential aspects of every piece of software. Any application constantly process various information, that very often require specific grouping and access strategies. This aspect is addressed by arrays and more advanced collection types. By using the Javonet framework, users gain ability to easily and effectively work with data structures originating from .NET Framework DLL. Every collection from .NET Framework DLL is treated as reference.

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 collections from .NET Framework DLL like they were available in Ruby but invocation must be performed through Javonet SDK API.

Working with Ruby lists from .NET Framework DLL

Javonet SDK contains various methods to interact with lists and consume the results in Ruby:

I code in:
# 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
string_type = called_runtime.get_type('System.String').execute

# get type for generic class
list_type = called_runtime.get_type('System.Collections.Generic.List`1', string_type).execute

# create instance of generic class
list_instance = list_type.create_instance.execute

# invoke instance's method
list_instance.invoke_instance_method('Add', 'one').execute
list_instance.invoke_instance_method('Add', 'two').execute
list_instance.invoke_instance_method('Add', 'three').execute
list_instance.invoke_instance_method('AddRange', %w[four five six]).execute

# get elements from list
response1 = list_instance.get_index(2).execute
response2 = list_instance[3].execute

# get value from response
result1 = response1.get_value
result2 = response2.get_value

# write result to console
puts result1
puts result2

In the snippet above, list specific to called technology framework is created.
Then, some elements are added to the list. Finally, this list can be handled through Javonet SDK, f.e. with getIndex method.

Working with Ruby dictionary from .NET Framework DLL

Javonet SDK contains various methods to interact with dictionaries and consume the results in Ruby:

I code in:
# 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
string_type = called_runtime.get_type('System.String').execute
double_type = called_runtime.get_type('System.Double').execute

# get type for generic class
dictionary_type = called_runtime.get_type('System.Collections.Generic.Dictionary`2', string_type,
                                          double_type).execute

# create instance of generic class
dictionary = dictionary_type.create_instance.execute

# invoke instance's method
dictionary.invoke_instance_method('Add', 'pi', Math::PI).execute
dictionary.invoke_instance_method('Add', 'e', Math::E).execute
dictionary.invoke_instance_method('Add', 'c', 299_792_458.0).execute

# get elements from dictionary
response1 = dictionary.get_index('pi').execute

# get value from response
result1 = response1.get_value

# write result to console
puts result1

In the snippet above, list specific to called technology framework is created.
Then, some elements are added to the list. Finally, this list can be handled through Javonet SDK, f.e. with getIndex 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