topic Re: Load Plug-in DLL Without Editing Config File in .NET Forum

Load Plug-in DLL Without Editing Config File

ahmedshawkey95 — Sat, 19 Aug 2017 23:03:11 GMT

I'm developing a windows form application that needs to open AutoCAD and load my plug-in DLL to send custom commands and lisp functions to it.

I'm using the following C# code and it works fine in my device but when I tried to run it another machines, I got the attached error message "Cannot load file or assembly...".

But it worked fine after editing AutoCAD config file "acad.exe.config" by adding :

<runtime> <loadFromRemoteSources enabled="true" /> </runtime>

Is there any other way to fix this error programmatically to avoid editing the config file manually? or is there a better way to load my plug-in DLL and call the lisp functions from it?

//1-Opening AutoCAD//

AcadApplication _acadApp;

const string progID = "AutoCAD.Application";//for all AutoCAD versions
try
{
_acadApp = (AcadApplication)Marshal.GetActiveObject(progID);
}
catch
{
try
{
Type acType = Type.GetTypeFromProgID(progID);

if (acType == null)
acType = Type.GetTypeFromProgID("AutoCAD.Application");

_acadApp = (AcadApplication)Activator.CreateInstance(acType, true);

}
catch (System.Exception ex)
{
CommonOperations.Log("Exception", ex.ToString());
}
}

//2-Opening DWG//

_acadApp.Documents.Open("myDrawingPath", Type.Missing, Type.Missing);

//3-Load My Plug-In DLL//

string appDirectory = AppDomain.CurrentDomain.BaseDirectory; // get the application directory
string dllLocation = $"{appDirectory}SolutionMetric.Qsurv.AutoCAD_Plugin.dll"; // get the plugin directory
if (File.Exists(dllLocation))
{
dllLocation = dllLocation.Replace(@"\", @"\\"); // so that the lisp can understand the directory
_acadApp.ActiveDocument.SendCommand("(command \"NETLOAD\"" + $@"""{dllLocation}"") "); //TODO:Causes error in the user's devices
}

//4-Call lisp functions from the plug-in//

_acadApp.ActiveDocument.SendCommand($@"(LoadItems {taskID} {fileID}) ");

Re: Load Plug-in DLL Without Editing Config File

norman.yuan — Mon, 21 Aug 2017 13:16:38 GMT

</runtime>

was introduced into .NET framework 4.0 when the code security execution in "sand box" mode, as an "security compromised" backward compatibility.

With AutoCAD .NET add-in, originally, when the DLL is placed in a network location, one can use his as quick/dirty solution. Since later AutoCAD versions added tigher code execution security, a DLL would not be considered safe not only when it locates outside of local drive, but also when it locates in local drive as long as it is not in a folder specified by "TrustedDomains" and "TrustedPaths".

You really need to understand the latest security settings for AutoCAD, instead of trying to use <loadFromRemote.../> in acad.exe.config, or trying to programmingly bypass security (which is equivalent to write virus/malicious code:-(). That is, you can either load your Add-in with AutoCAD's auto plug-in loading mechanism, or setup "TrustedDomains/Paths", so that the code is considered by AutoCAD as safe code.

Re: Load Plug-in DLL Without Editing Config File

Anonymous — Mon, 21 Aug 2017 15:06:55 GMT

I had the same issue even after I fooled with the

"<loadFromRemoteSources enabled="true" />"

The one work around I found was to have the other machine, right click the dll, and go to its properties. In the security area, check the box to unblock the dll, then apply and ok.

This worked for me and my office.

Re: Load Plug-in DLL Without Editing Config File

norman.yuan — Mon, 21 Aug 2017 15:24:21 GMT

This issue is/may not be the same as the OP has.

The issue you had is because the DLLs you installed on other computer somehow being transferred via the Internet (say, you email the Dlls files, even you zipped it up) to the user, or your company has complicated network that may connected to user with VPN via the Internet), thus Windows OS automatically flag this executable file as "potentially unsafe". You can remove this "unsafe" flag as you described.

Regardless whether the OP has this issue or not, he/she should be loading Acad DLLs following AutoCAD security guidance, rather than change acad.exe.config, or try to programmatically write "malicious" code to bypass security.