Topic: start command with acaddoc

[sybold]

i'm in the progress of converting old vba code to .net, and we have a call in the acaddoc.lsp to run a vba routine. now is my question can i do the same for a .net created command.

[Kerry]

You could try it by 'netload'ing the .net DLL and running the registered command.

[dgorsman]

Or, write the core function in dotNET and provide separate interface wrapper methods - one for a command-line definition and one for a LISP function call.  That way the same procedure can be called by both command invocation and through LISP.

[irneb]

Or, write the core function in dotNET and provide separate interface wrapper methods - one for a command-line definition and one for a LISP function call.  That way the same procedure can be called by both command invocation and through LISP.

Depends what you want to do. Even the DotNet command wrapper allows script and lisp callable commands. It's when you want to obtain information FROM the dotnet function that you'd need a LispFunction wrapper instead and/or as well.

If it's simply a situation of you want to autoload your dotnet and have a command run each time a dwg is opened. For the autoloading the "cleanest" way is through registry: http://through-the-interface.typepad.com/through_the_interface/2006/09/automatic_loadi.html

Unfortunately the only other way to load DotNet DLL's (except through DotNet/ARX programming) is using the NetLoad command. What I'd actually want was a netload function similar to arxload - that way it would be a lot cleaner (no need to add command calls into a startup defun).