Retrieve .NET Framework DLL array in Perl app

This article shows how to retrieve array from called technology.

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.

Custom .NET Framework DLL with array handling

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

Snippet below represents the sample code from .NET Framework DLL that has methods which return or process the arrays:

namespace TestClass
{
	public class TestClass
	{
		public TestClass() { }

		public string[] Get1DArray()
		{
		    return new string[] { "one", "two", "three", "four", "five" };
		}
		
		public string[,] Get2DArray()
		{
		    return new string[,] { { "S00", "S01" }, { "S10", "S11" } };
		}
		
		public double AddArrayElementsAndMultiply(double[] myArray, double myValue)
		{
		    double sum = 0;
		    foreach (double element in myArray)
		    {
		        sum += element;
		    }
		
		    return sum * myValue;
		}
	}
}
public string[] Get1DArray()
{
    return new string[] { "one", "two", "three", "four", "five" };
}

public string[,] Get2DArray()
{
    return new string[,] { { "S00", "S01" }, { "S10", "S11" } };
}

public double AddArrayElementsAndMultiply(double[] myArray, double myValue)
{
    double sum = 0;
    foreach (double element in myArray)
    {
        sum += element;
    }

    return sum * myValue;
}

Retrieve .NET Framework DLL array in Perl application

With Javonet SDK it is possible to retrieve array from called technology and cast it to Perl array.

In the snippet above, get1DArray method is used to get reference to 1D array from .NET Framework DLL. Method retrieveArray is used to get the whole array from called technology and save it to local variable.

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.