Author Topic: dll not working in Autocad 2016 (see Link)  (Read 1931 times)

0 Members and 1 Guest are viewing this topic.


CAB

  • Global Moderator
  • Seagull
  • Posts: 10401
Re: dll not working in Autocad 2016 (see Link)
« Reply #1 on: June 19, 2016, 11:05:50 AM »
I posted in that thread so Gile will get a notification & perhaps reply.
I've reached the age where the happy hour is a nap. (°¿°)
Windows 10 core i7 4790k 4Ghz 32GB GTX 970
Please support this web site.

gile

  • Gator
  • Posts: 2507
  • Marseille, France
Re: dll not working in Autocad 2016 (see Link)
« Reply #2 on: June 19, 2016, 04:49:44 PM »
Hi,

For AutoCAD 2013 and later you have to NETLOAD LispVpLayer_19.dll.
You may have to "unblock" the ZIP file (or the dll): right click > Properties > General tab > Unblock.

If you still have problem, please give a more detailed description.
Speaking English as a French Frog

reyas1123

  • Newt
  • Posts: 50
Re: dll not working in Autocad 2016 (see Link)
« Reply #3 on: June 20, 2016, 07:58:15 AM »
hI

Hi,
I did try to unblock and do the Netload but I got this error.

Thanks

Command: NETLOAD
Cannot load assembly. Error details: System.IO.FileLoadException: Could not load file or assembly 'file:///D:\Labi\00-Layer\LispVpLayer(Freeze Layer in Vport)\LispVpLayer_19.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
File name: 'file:///D:\Labi\00-Layer\LispVpLayer(Freeze Layer in Vport)\LispVpLayer_19.dll' ---> System.NotSupportedException: 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 loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
   at System.Reflection.Assembly.LoadFrom(String assemblyFile)
   at Autodesk.AutoCAD.Runtime.ExtensionLoader.Load(String fileName)
   at loadmgd()

gile

  • Gator
  • Posts: 2507
  • Marseille, France
Re: dll not working in Autocad 2016 (see Link)
« Reply #4 on: June 20, 2016, 09:19:28 AM »
Seeing the error message, I suspect two possible reasons:
- the DLL is not locally registered (it's on a server)
- the DLL is not properly unblocked
Speaking English as a French Frog

Jeff H

  • Needs a day job
  • Posts: 6150
Re: dll not working in Autocad 2016 (see Link)
« Reply #5 on: June 20, 2016, 01:46:14 PM »
Looking at error message I will bet your D: drive is mapped to a network location?


reyas1123

  • Newt
  • Posts: 50
Re: dll not working in Autocad 2016 (see Link)
« Reply #6 on: June 21, 2016, 03:04:20 AM »
It has something to do with network access. its working fine now

Thanks Gile.

Rey