There is an instance of this class for every open drawing document. This file contains the DsAddinDocument class that handles events thrown by open drawing documents.
This file also contains the DraftSight ICommand event callback functions. There is an instance of this class for every add-in command. This file contains the DsAddinCommand class that handles events thrown when a command executes. This file contains the main add-in class. This file contains the class to handle the add-in's images.
To get acquainted with the contents of the files created by the template, examine the Solution Explorer and the following table. The COM server for the add-in is created when the project is created.
See the Microsoft Visual Studio documentation for details on how to add and remove references in a project. NOTE: After upgrading to a new version of the DraftSight API, you must replace references to DraftSight API type libraries and primary interop assemblies in existing DraftSight API projects developed in Microsoft Visual Studio. The DraftSight install_dir path is typically C:\Program Files\Dassault Systemes\DraftSight. The DraftSight API type libraries and primary interop assemblies are: DraftSight type libraries and primary interop assemblies NOTE: Italicized words in this topic and throughout the Help indicate where you should substitute the actual names of the entities that exist on your computer, in your add-in project, and elsewhere. Sample Projects are available to DraftSight users with network licenses.
DraftSight type libraries and primary interop assemblies.This topic also contains general information about the DraftSight API. This topic contains information to help you get started with automating and creating add-ins for DraftSight.