Hi Stephan,

Interop PowerScript => .NET requires COM Callable wrapper through OLEObject or other kind of interop.

Coming soon is .NET interop where PB IDE generates proxy objects. No OLEObject, no COM callable wrapper. I expect demos at Elevate conference which is late October.

Simplicity of PowerScript as we know it. Assembly loaded and .NET object instantiated behind the scenes.

HTH /Michael

As Michael stated, it is on the roadmap, and you will most likely see it at elevate this month. While you are at elevate, you will be able to ask appeon staff directly whether your use case will work with what they are doing:

https://www.appeon.com/developers/roadmap

"Call C# assemblies from PowerScript apps;"

Adding to what Michael said, the .NET interop feature being natively added to PowerBuilder in 2019 R2 will allow you to interop with non-visual C# assemblies. 

If it is coded in other .NET languages (e.g. VB.NET) or if it is a visual object, then the interop feature would not apply and you would need to use the COM callable wrapper workaround.

First of all, thank you for your answers.

I proceeded as follows:
1. I downloaded a c# interop form toolkit and wrote a simple dll called nettest.dll.
2. I registered this dll with regasm "nettest.dll" /codebase.
3. I generated an OleObject (new -> standard class) and named it n_oleobject_test

Sourcecode (PowerBuilder):
n_oleobject_test lnv_test
lnv_test = create n_oleobject_test
lnv_test.Connecttonewobject("NetTest.NetTest")
Messagebox("your default printer is?",String(lnv_test.of_getPrinter() ))
lnv_test.Disconnectobject( )
Destroy lnv_test

Sourcecode (visual studio):
public String of_getPrinter()
{
//get default printername
PrinterSettings ps = new PrinterSettings();
return ps.PrinterName ;
}

This works fine, but is this the right way at this time until PowerBuilder 2019 R2 will be released?