How jhonatan9a/api-.net-autocad works
Main components
• AutoCAD Environment: Represent the AutoCAD host application where the plugins run.
• Plugin Projects: Each subproject (Base, BlockInsert, ExportPostGIS, RankPolyline) builds its own DLL. Each one acts as an independent module that implements a command to extend AutoCAD’s functionality.
• Development Environment: Show Visual Studio configured for .NET Framework 8. Label configuration elements such as references to AutoCAD libraries (AcDbMgd.dll, AcMgd.dll, AcCoreMgd.dll) which are critical.
• External Dependencies: Mark the AutoCAD .dll files (loaded from C:\Program Files\Autodesk\AutoCAD 20XX\Managed\) and any other external scripts such as SQL scripts and DWG sample files that support testing or demonstration.
Relationships and interactions
• That the Visual Studio development environment (and its configuration) compiles the various projects into DLLs.
• Data flows such as:
• From AutoCAD: User command triggers (e.g., entering the command name).
• To Plugin: Execution of the command’s functionalities (block insertion, exporting data to PostGIS, ranking polyline segments, etc.).
Important architectural patterns
• Clear separation between compile-time (Visual Studio/.NET Framework) and runtime environment (AutoCAD).
• Environment configuration and reference management (ensuring the proper binaries are not copied locally to prevent conflicts).
Relevant technologies and frameworks
• .NET Framework 8 as the target platform.
• Visual Studio as the development IDE.
• AutoCAD’s API via its managed DLLs.
• The pattern of loading external command libraries through the NETLOAD process.