.NET Cookbook 10: Single-Source Dual-Target .CSPROJ Architecture for AutoCAD & GstarCAD Plugins

1. Single-Repository Multi-Targeting Architecture: Compiling AutoCAD & GstarCAD 2027 Plugins from One SDK-Style `.csproj`

Maintaining two separate Git repositories—one for AutoCAD and one for GstarCAD—inevitably leads to bug-fix drift and doubled QA overhead. Because the GstarCAD .NET API mirrors AutoCAD's class structure 1:1, software architects can configure a single modern SDK-style `.csproj` file with `Release_GstarCAD;Release_AutoCAD` and conditional MSBuild `` blocks to compile both binaries simultaneously.

Critical Kernel & Memory Safety Rule: Create a single `CadApiAliases.cs` file using C# 10+ `global using` directives guarded by `#if GSTARCAD` (`global using CadApp = Gssoft.GstarCAD.ApplicationServices.Application;`) vs `#elif AUTOCAD` (`global using CadApp = Autodesk.AutoCAD.ApplicationServices.Application;`). In your MSBuild `.csproj`, always set `False` (`Copy Local = False`) on `GsMgd.dll` and `GsDbMgd.dll` so the output folder isn't polluted with host CAD assemblies that degrade plugin load performance.

2. Managed C# .NET Implementation (GRX / .NET / LISP)

Reference GsMgd.dll and GsDbMgd.dll (with Copy Local = False) in your C# class library project to execute .NET Cookbook 10: Single-Source Dual-Target .CSPROJ Architecture for AutoCAD & GstarCAD Plugins inside the GstarCAD 2027 CLR runtime:

// Dual-Target GlobalUsings.cs for GstarCAD 2027 & AutoCAD Compatibility
#if GSTARCAD
global using CadApp = Gssoft.GstarCAD.ApplicationServices.Application;
global using Gssoft.GstarCAD.Runtime;
global using Gssoft.GstarCAD.DatabaseServices;
global using Gssoft.GstarCAD.Geometry;
global using Gssoft.GstarCAD.EditorInput;
#else
global using CadApp = Autodesk.AutoCAD.ApplicationServices.Application;
global using Autodesk.AutoCAD.Runtime;
global using Autodesk.AutoCAD.DatabaseServices;
global using Autodesk.AutoCAD.Geometry;
global using Autodesk.AutoCAD.EditorInput;
#endif

3. ObjectARX-to-GRX & .NET API Porting Matrix

When dual-targeting plugins for both AutoCAD and GstarCAD 2027 from a unified Git repository, reference the following symbol, header, and assembly mapping table:

4. Memory Management, Thread Safety & QA Checklist

• Deterministic Object Closure & Transaction Disposal: In C++ GRX, every acdbOpenObject() call that returns Acad::eOk must be paired with an explicit pObj->close() before starting a command or returning control to the editor. In C# .NET, always wrap StartTransaction() inside a using block and explicitly call tr.Commit().
• Document Locking from Modeless Contexts: Whenever modifying the active DWG database from a modeless WPF PaletteSet, WinForms dialog, or external COM event, acquire a write lock via doc.LockDocument() to prevent eLockViolation exceptions.
• Multi-Core Fiber & Main-Thread Discipline: The DWG database (`AcDbDatabase`) is not thread-safe for concurrent writes. Offload heavy geometric calculations or SQL/REST I/O to background worker threads, then marshal database mutations back to the main CAD UI thread.

Production Compilation, Packaging & Enterprise Deployment Guide

When deploying this developer recipe into commercial enterprise production, development leads should configure automated CI/CD build agents (GitHub Actions or Azure DevOps) using MSBuild command-line flags. Ensure that all dependent assemblies (such as GsMgd.dll and GsDbMgd.dll) have their reference property set to Copy Local = False (Private=False) to prevent deployment conflicts with the host GstarCAD 2027 application folder:

• Target Framework Alignment: For C# .NET plugins, target .NET Framework 4.8 or .NET 8.0 Windows Desktop runtime depending on your GstarCAD host version. For C++ GRX extensions, compile using Visual Studio 2022 (MSVC v143) with the platform toolset set to 64-bit (x64) and Character Set set to Unicode.
• Registry-Free Autoloading (.bundle): Package your compiled binary and menu CUIX files into an Autodesk/GstarCAD-compatible Application Package bundle folder (e.g., EnterprisePlugin.bundle/PackageContents.xml) and deploy directly to %APPDATA%\Autodesk\ApplicationPlugins or %PROGRAMDATA%\Gstarsoft\ApplicationPlugins for automatic silent loading without requiring administrative Windows registry rights.
• Automated Exception Trapping & Telemetry: Always wrap top-level command methods and event handlers inside structured try-catch or AutoLISP vl-catch-all-apply blocks to log diagnostic stack traces to corporate log repositories rather than letting unhandled exceptions crash the host drawing session.