Execute method in C# app

Because invocation context is building the intent of executing particular expression on target environment, we call the initial state of invocation context as non-materialized. The non-materialized context wraps either single command or chain of recursively nested commands.

namespace SampleProgram {
	using Javonet.Netcore.Sdk;
	internal class Program {
		private static string resourcesDirectory = ".";
		static void Main(string[] args) {

			// use Activate only once in your app
			Javonet.Activate("your-license-key");
			
			// create called runtime context
			var calledRuntime = Javonet.InMemory().Ruby();
			
			// construct an invocation context - this invocationContext in non-materialized 
			var invocationContext = calledRuntime.GetType("Math").
			    InvokeStaticMethod("sqrt", 2500);
			
			// execute invocation context - this will materialize the invocationContext
			var response = invocationContext.Execute();
		}
	}
}// use Activate only once in your app
Javonet.Activate("your-license-key");

// create called runtime context
var calledRuntime = Javonet.InMemory().Ruby();

// construct an invocation context - this invocationContext in non-materialized 
var invocationContext = calledRuntime.GetType("Math").
    InvokeStaticMethod("sqrt", 2500);

// execute invocation context - this will materialize the invocationContext
var response = invocationContext.Execute();

Commands are becoming nested through each invocation of methods on Invocation Context. Each invocation triggers the creation of new Invocation Context instance wrapping the current command with new parent command valid for invoked method.

Developer can decided on any moment of the materialization for the context taking full control of the chunks of the expression being transferred and processed on target runtime.

Execute method in C# app

Additional references