Is the .dll on a Netwok?
Interesting... I've heard of some having issues with that, and just tried it. I copied a DLL to the network (where I have write access), and did a NETLOAD. The DLL came in fine, and the CommandMethods worked... for the first few. Then It crashed my ACAD. LoL
The DLL is compiled using framework 3.5, and I've been testing with 2011 (via Debug), but the test mentioned above was done with 2009 (also .NET 3.5).
What I specifically found interesting, that I was previously unaware of, was in above mentioned DLL I have a simple .NET toggle of MBUTTONPAN SysVar CommandMethod that does the same as a LISP Defun that I use. Anyway, after testing the .NET version and it working, I reloaded my LISP, and the .NET version was not redefined as the LISP Defun as I was expecting.
Is there a way around this? I want to make my code available to others, and not mico-manage other's code function naming. I'd be pretty pissed if I wanted to use <AnyName> and could not as a result of some A-Holes NETLOAD. Avoiding this issue would be highly advantageous.