As you’re probably mostly aware, many of our 2012 products use. NET 4 as standard. This has proven “interesting” (i.e. challenging) when it comes to loading – for example – plugin DLLs downloaded from the web, due to. NET’s updated security model. Our ADN Plugins of the Month on Autodesk Labs are a prime example: most were posted prior to Auto CAD 2012 shipping, but when downloaded locally and NETLOADed into Auto CAD 2012, very often a security error gets reported: Cannot load assembly. Error details: System. IO. File Load Exception: Could not load file or assembly ' Files\ Autodesk\ Auto CAD 2012 – English\ ADNPlugin- QRCodes.dll' or one of its dependencies. Operation is not supported. ( Exception from HRESULT: 0x80131515) File name: ' C:\ Program Files\ Autodesk\ Auto CAD 2012 – English\ ADNPlugin- QRCodes.dll ' -> System. Not Supported Exception: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the. NET Framework. This release of the. NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the load From Remote Sources switch. See for more information. It also happens in our other products making use of. NET 4 ( Revit, in particular). This is now by far the most common problem reported regarding these plugins, in spite of efforts to document the problem and the solution. ( There’s also some helpful information on MSDN, in case.) When this problem first arose, it took a while for it to be understood (by me, at least). If you build the DLLs locally, clearly there isn’t a problem. And if *.autodesk.com happens to be in your trusted sites zone in Internet Explorer (which it is for most Autodesk employees, understandably) then the issue.
PROBLEM You cannot execute a project across the network in. NET Framework 4.0. You receive an error that reads: System. Not Supported Exception: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the. NET Framework. This release of the. NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the load From Remote Sources switch. See for more information. SOLUTION There was a security change introduced in. NET Framework 4.0 which by default restricts.dll access from network locations. Modify the Art Of Test. Runner.exe.config file located in the Test Studio installation folder. By default the location is: C:\ Program Files (x86)\ Telerik\ Test Studio\ Bin\ Open the file Art Of Test. Runner.exe.config with Notepad (or any text editor) and add the following lines within the configuration section: It should now look like this: Users with earlier versions of. NET may see this error: System. Reflection. Target Invocation Exception: Exception has been thrown by the target of an invocation. -> System. Security. Security Exception: That assembly does not allow partially trusted callers. If you receive this error, upgrade to. NET Framework 4.0.
Loading Assemblies from Network Locations. NET's default policy does not allow for loading of. NET assemblies (.dll files) from remote network locations. When attempting to load an assembly off a network path instead you get a network exception that complains about security policy. You can override this behavior with a configuration setting in your EXE's.config file. The key is the load From Remote Source key which can be set to allow remote. DLL loading to occur. Note that a.config file must be set up for whatever top level EXE file is running the application. This means: Your App.exe.config (your own EXE) VFP9.exe.config (running VFP IDE) Traditional Fixes using CASPOL The above is a new feature of the. NET framework and it should work with recent installs of. NET 2.0 or later. However, older. NET 2.0 installs don't respect this key in the config file. You can adjust. NET Security with the CASPOL. EXE command line tool that lives in the. NET Framework directory (ie. C:\ Windows\ Microsoft. NET\ Framework\v 7). There's more information on CASPOL on MSDN: CASPOL. EXE docs UI Wrapper for CASPOL The easiest way to do this is by disabling CAS security entirely with: C:\ Windows\ Microsoft. NET\ Framework\v 7\ CASPOL.exe - Security off which disabled. NET CAS security. While this works it's very intrusive and removes the core CAS Security engine for all. NET applications and components. To disable CAS security for specific assemblies you can use the following: Cas Pol.exe -machine -addgroup All_ Code -url C:\wcconnect\ww Dot Net Bridge.dll Full Trust Note in order to run CASPOL. EXE you have to have full administrative rights and this configuration step should be performed as.
Download Now