DOTNET DLL and RunOnClient

mvendert

We've created a .NET DLL (For nav 2013R2), which need to be run on the client. Hence, the RunOnClient property needs to be set to Yes.

But sometimes people tend to forget this and get some unexpected behavior.

You could argue we simply not install this DLL in the service tier add-in folder, but for now the dll contains more classes from which only one needs to run on the client.

Can one determine from the .NET code if it was created in a 'client' context and not on the service tier?
If so, an error could be thrown from this class. Any ideas?

Marc.

thegunzo

@mvendert

By adding a simple static method to your DLL you should be able to do this.

The static method could respond with an environment variable or you can use reflection (System.Reflection.Assembly.'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089') to get Assembly.GetExecutingAssembly.Location that should give you a file name.

massimopasquali

Hi guys,

I have need the same necessity, I have to do a DLL in C# and call this from a codeunit. I don't know how can do it, I have realized that I need to use a Global Variables - DotNet ( I suppose).

Can you post me an example, please