topic Re: List of loaded assemblies in .NET Forum

List of loaded assemblies

Anonymous — Mon, 12 Mar 2007 14:46:13 GMT

APPLOAD shows the files that are currently loaded and where they are located. Is there a was to access the names of loaded .NET dlls and their location?

Re: List of loaded assemblies

Anonymous — Mon, 12 Mar 2007 15:34:51 GMT

AppDomain.CurrentDomain.GetAssemblies();

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006/2007
http://www.acadxtabs.com

wrote in message news:5515294@discussion.autodesk.com...
APPLOAD shows the files that are currently loaded and where they are located. Is there a was to access the names of loaded .NET dlls and their location?

Re: List of loaded assemblies

Anonymous — Mon, 12 Mar 2007 17:05:14 GMT

And with a little help from System.Reflection, you can scan each assembly for methods using the CommandMethodAttribute to get the command(s) it is exposing to AutoCAD...

Re: List of loaded assemblies

Anonymous — Mon, 12 Mar 2007 21:27:30 GMT

but not with lisp right?
I care because my key-ins routine is lisp. It creates two letter commands for various routines.
I can test for lisp functions, arx's loaded, dvb, vlx, lots of things, but not .net assemblies it seems.

It does not seem to matter too much as you can double load a .dll with no issues.
so my key-in might be:
(DEFUN C:CCM () (princ "\nChange layer properties Modeless")
(setvar "cmdecho" 0)
(COMMAND "netload" "ChlayCoLtNetR16.dll")(command "Chlaycolt") <-- runs load command every time before running
(princ)
)

where as with lisp, I only load it if needed:
(if (not c:chlaycolt)(load "chlaycoltr16.lsp")) then run...(c:chlaycolt)

It seems that loading a .net assembly every time you run it is fine as the load statement gets ignored if already
loaded.

Tony Tanzillo
|>AppDomain.CurrentDomain.GetAssemblies();
James Maeding
Civil Engineer and Programmer
jmaeding - at - hunsaker - dotcom