Function Syntax: LispsLoader Version: 1.0 Date: 11.08.2026 3:19:48PM Version: 1.0 Date: 11.08.2026 3:19:52PM N/A Description 🧩 LispLoader v1.0.000 is an AutoCAD and Civil 3D .NET startup loader that reads LoaderConfig.txt and safely processes configured LSP VLX FAS and DLL program files. 📄 One configured file failing does not intentionally stop the remaining load sequence and all results are written to the AutoCAD command line and a rolling disk log. ⚙️ The plugin starts its configured load sequence immediately when the compiled LispLoader DLL is loaded into AutoCAD. Function Syntax Startup action: NETLOAD LispLoader.dll Configuration file: LoaderConfig.txt Log file: LispLoader.log Primary Workflow 1. NETLOAD LispLoader.dll into AutoCAD. 2. AutoCAD calls the plugin Initialize method. 3. The plugin prints the version and build timestamp. 4. LoaderConfig.txt is read and blank or commented lines are ignored. 5. Configured files are resolved and processed one by one. 6. LSP VLX and FAS files are sent to the active AutoCAD document as load expressions. 7. DLL files are loaded into the AppDomain and registered through AutoCAD ExtensionLoader. 8. A final OK FAILED and SKIPPED summary is written to the log. Functionalities ✅ Configuration driven loading - uses LoaderConfig.txt as the source list. ✅ LSP loading - supports AutoLISP source files. ✅ VLX loading - supports Visual LISP executable files. ✅ FAS loading - supports compiled AutoLISP files. ✅ DLL loading - loads .NET assemblies with Assembly.LoadFrom and ExtensionLoader. ✅ Relative and absolute paths - accepts both path types in the configuration. ✅ Failure isolation - continues the loop when individual files are missing or return a handled failure. ✅ Command line logging - reports loading progress inside AutoCAD. ✅ Rolling disk log - writes LispLoader.log and rotates it at 5 MB. ✅ Version banner - prints version and build timestamp when the plugin initializes. Important Notes ⚠️ Project version is 1.0.000. ⚠️ The provided LoaderConfig contains example entries for DLL LSP FAS and VLX files. ⚠️ The README recommends placing DLL entries before dependent LISP files. ⚠️ The LSP load path is sent asynchronously with SendStringToExecute so the immediate OK log represents successful dispatch rather than a full parser level verification of the target LISP result. ⚠️ An active AutoCAD document is required for LSP VLX and FAS dispatch. SEO Keywords 🏷️ AutoCAD 🏷️ Civil 3D 🏷️ LispLoader 🏷️ AutoLISP loader 🏷️ VLX loader 🏷️ FAS loader 🏷️ DLL loader 🏷️ LoaderConfig 🏷️ ExtensionLoader 🏷️ AutoCAD startup 🏷️ Rolling log 🏷️ CAD automation