Hi there

I seem to have some trouble sharing my plugins with my colleagues using workgroups.
I have created a workgroup and copied my .dll’s there (c# plugins). The plugins load fine on my own machine but on the other machines I get the following error:

‘ ERROR : 2262 - This plug-in could not be loaded:
‘

This only applies to compiled plugins, jScript and python scripts load just fine.
Am I doing something wrong here?

Cheers
Jacob

I think it is a .NET security issue.
Sorry, that’s all I got...I’m still trying to find the answer myself.

do you know of any workarounds (apart from distributing the plugins directly to the other machines)?

[quote=RedBjarne;10290]do you know of any workarounds (apart from distributing the plugins directly to the other machines)?

We had that problem with realtime shaders.  Make sure the workgroup .dll path is defined in the user’s PATH environment variable.

It is .NET policy issue, the assembly (plugin) needs to be located by the .net runtime in the gac....

1) create a strong name key for the assembly
- in devenv open c# project properties and go to ‘Signing’ tab
- check ‘Sign the assembly’ and enter a strong name key file (select <New...> in listbox)
- recompile

2) add the assembly to the GAC
e.g.
C:\>gacutil /i \\server\example\workgroup\Application\Plugins\CSharpScripting.dll

Thanks for the reply but unfortunately it does not work for me.

I am compiling the plugins on my workmachine and the copies them to a central server, can this be part of the issue?