Autoload .NET dll

[Anonymous]

From the help files:
"To load a managed application, enter NETLOAD at the AutoCAD Command prompt
and browse to the desired DLL file. Managed applications are unloaded only
when AutoCAD exits."

Does this mean that to use my .NET program in AutoCAD my users have to use
"Netload"?
That doesn't seem right. Not when DVB and ARX etc. files can be added to the
Startup Suite so that they will auto-load.

After searching this ng the only thing I found was some (ugh) LISP
programming to add to startup.

Is there a better way to autoload my .NET dll?

Thanks,
Mark

[Anonymous]

dll's can be demand loaded by registering your app with the windows
registry.

greg hoyt

"Mark Johnston" wrote in message
news:5227557@discussion.autodesk.com...
From the help files:
"To load a managed application, enter NETLOAD at the AutoCAD Command prompt
and browse to the desired DLL file. Managed applications are unloaded only
when AutoCAD exits."

Does this mean that to use my .NET program in AutoCAD my users have to use
"Netload"?
That doesn't seem right. Not when DVB and ARX etc. files can be added to the
Startup Suite so that they will auto-load.

After searching this ng the only thing I found was some (ugh) LISP
programming to add to startup.

Is there a better way to autoload my .NET dll?

Thanks,
Mark

[Anonymous]

How does that work?

"Gregory A. Hoyt" wrote in message
news:5227712@discussion.autodesk.com...
dll's can be demand loaded by registering your app with the windows
registry.

greg hoyt

"Mark Johnston" wrote in message
news:5227557@discussion.autodesk.com...
From the help files:
"To load a managed application, enter NETLOAD at the AutoCAD Command prompt
and browse to the desired DLL file. Managed applications are unloaded only
when AutoCAD exits."

Does this mean that to use my .NET program in AutoCAD my users have to use
"Netload"?
That doesn't seem right. Not when DVB and ARX etc. files can be added to the
Startup Suite so that they will auto-load.

After searching this ng the only thing I found was some (ugh) LISP
programming to add to startup.

Is there a better way to autoload my .NET dll?

Thanks,
Mark

[Anonymous]

http://discussion.autodesk.com/thread.jspa?messageID=4531456

"Mark Johnston" wrote in message
news:5227748@discussion.autodesk.com...
How does that work?

"Gregory A. Hoyt" wrote in message
news:5227712@discussion.autodesk.com...
dll's can be demand loaded by registering your app with the windows
registry.

greg hoyt

"Mark Johnston" wrote in message
news:5227557@discussion.autodesk.com...
From the help files:
"To load a managed application, enter NETLOAD at the AutoCAD Command prompt
and browse to the desired DLL file. Managed applications are unloaded only
when AutoCAD exits."

Does this mean that to use my .NET program in AutoCAD my users have to use
"Netload"?
That doesn't seem right. Not when DVB and ARX etc. files can be added to the
Startup Suite so that they will auto-load.

After searching this ng the only thing I found was some (ugh) LISP
programming to add to startup.

Is there a better way to autoload my .NET dll?

Thanks,
Mark

[Anonymous]

Thanks.
I didn't think to search the VBA group.

=Mark

"Kerry Brown" wrote in message
news:5228415@discussion.autodesk.com...
http://discussion.autodesk.com/thread.jspa?messageID=4531456

"Mark Johnston" wrote in message
news:5227748@discussion.autodesk.com...
How does that work?

"Gregory A. Hoyt" wrote in message
news:5227712@discussion.autodesk.com...
dll's can be demand loaded by registering your app with the windows
registry.

greg hoyt

"Mark Johnston" wrote in message
news:5227557@discussion.autodesk.com...
From the help files:
"To load a managed application, enter NETLOAD at the AutoCAD Command prompt
and browse to the desired DLL file. Managed applications are unloaded only
when AutoCAD exits."

Does this mean that to use my .NET program in AutoCAD my users have to use
"Netload"?
That doesn't seem right. Not when DVB and ARX etc. files can be added to the
Startup Suite so that they will auto-load.

After searching this ng the only thing I found was some (ugh) LISP
programming to add to startup.

Is there a better way to autoload my .NET dll?

Thanks,
Mark