Have you configure the security settings for the corresponding .NET
framework (1.x or 2.0) on the targeting computer? Since you load the .NET
assemblies from a network share, by default, the .NET Framework treats code
from outside of the running computer as unsafe and will not run it.
You use MS .NET Framework Configuration applet in Control Panel or
commandline tool CASPOL.exe to configure security settings of .NET
Framework. Common approach is to create a code group that points to the
network share and give the code group required trust, just enough to run
your .NET app.
wrote in message news:5334442@discussion.autodesk.com...
I'm having errors loading assemblies on other computers other than the one I
used to develop. This is what I did: compile the assembly and place its
entire folder with all the references it needed in a server. Open AutoCAD in
my computer, ensure the commands I defined weren't available, loaded the
assembly directly from the server and run a command, which is now available
cause it's part of the assembly. If I try to do the exact thing in other
computers of the network (except for the compiling of course) the commands
never become available, even if I am loading the same assembly from the same
place, can anybody tell me what am I doing wrong?