Hi Luca De Mori,

Assuming that you have installed all the libraries, did you setup the engine to access R features?

Regards,

Hi Luca,

You should be able to use any .NET assembly DLL in your C# project. However, since R is not native .NET, are you using R.NET or something similar?

thanks for your answers ...

yes, in my project I have the RDotNet libraries v. 1.7.0.0 and, yes, the DLL are included in my XIF

You could try to use some GenericExtendedActions.LogMessage statements in your C# code to see up to what point the Extension works as expected.

Hi Kilian ... sorry but I don't know absolutely what you're talking about ...

do you have some links / material about that ?

The closest there is to documentation I know of is this.

Hello,

What Kilian was suggesting was using the code:

"GenericExtendedActions.LogMessage(AppInfo.GetAppInfo().OsContext, "<Message>", "<ModuleName>");"

to "debug" your C# code.

You can replace <Message> with the piece of data (variables or whatever) that you want to check and <ModuleName> with the name of the module (eSpace) that you are testing. This line of code will result on a output that you can read on Service Center on the "General" tab.

By using this you can check how far your extension went running properly and you can check the information on the variables.

thank you Kilian and Tiago ...

do you use it ? Because the first "warning" I have is Visual Studio is that "GenericExtendedActions.Audit" is depracated ... it tells me to use "LogMessage" instead ...

Erm... both me and Tiago said to use "LogMessage"???

Yes. I have used it to do debugging and check some values on my C# variables.

That warning is correct. You should now use "GenericExtendedActions.LogMessage" like Kilian and I showed you.