AUTOLOAD

Short answer

Two related AutoCAD mechanisms for loading plugins on demand: the (autoload) LISP function and the auto-load registry/bundle keys used for .NET DLLs.

AUTOLOAD has two distinct meanings. In LISP, (autoload "file" '("CMD1" "CMD2")) tells AutoCAD to load file.lsp the first time the user types CMD1 or CMD2 — deferred loading without making the user APPLOAD. For .NET plugins, 'auto-load' refers to registering a DLL under HKCU/Applications or shipping it as an AutoCAD .bundle so AutoCAD calls NETLOAD on it at startup. Most installer-based commercial plugins use the bundle approach because it survives AutoCAD upgrades.

Related guides

How to NETLOAD a .NET Plugin in AutoCAD

Load a C# / VB.NET plugin DLL into AutoCAD with NETLOAD, troubleshoot common load errors, and set up auto-load so you don't NETLOAD every session.

Related terms

NETLOAD

The AutoCAD command that loads a managed .NET plugin DLL into the running session.

.NET plugin

A managed assembly (C#/VB.NET DLL) that uses Autodesk's .NET API to add commands and behaviour to AutoCAD or Civil 3D.

AutoLISP

Autodesk's dialect of LISP, built into AutoCAD since 1986, used to write custom commands and automate drawings.