Page Comparison

ARES Commander provides .NET API which that lets you author third party Plugin Software for ARES Commander.

Supported API Sets 

ARES Commander supports 3 three API sets which that you can be used use independently.

1. .NET Classic API
2. ARES COM API
3. CFx .NET (SWIG generated .NET API version of ARES C++ SDK)

Creating a .NET Classic Plugin:

1. Create a new

...

1. C# or VB.NET

...

1. project using the Visual Studio project creation Wizard(  **minimum requirement .NET Framework v4.5)
   
   Image Modified

...

1. From Solution Explore

...

1. , add references of TD_Mgd_x.xx_xx*.dll

...

1. and FxCoreMgd_x.xx_xx.dll

...

1. from the ARES Commander installation folder.
   
   Image Modified
   

...

1. 
   You can

...

1. see all available NameSpaces, Classes, Methods, and Properties in each assembly

...

1. in the Object Browser.
   
   Image Added
              

...

2. Rename Class1.cs

...

1. to PluginCommands.cs

...

1. . This changes the class Class1 to class PluginCommands

...

1. , as in the following example.
   
   Image Modified
2. Defining a command

...

1. uses Teigha.Runtime namespace to access CommandMethod method

...

1. attribute and

...

1. adds a method

...

1. , such as AnyFunctionName that has this attribute.

...

1. The following example defines the MySampleCommand command which

...

1. you can run later in ARES Commander, from the command prompt.
   You can define all types of in-process

...

1. plugin using a similar procedure.
   Image Added
2. Build the sample project

...

1. to generate PluginCommans.dll or <YourProjectName.dll>.

...

1. Start ARES Commander and type NETLOAD

...

1. at the command

...

1. prompt. Next, browse and load the plugin dll

...

1. (PluginCommands.dll

...

1. ).
   The coommand window displays a confirmation message.
2. Run

...

1. MySampleCommand, which executes the AnyFunctionName method

...

1. . 

Accessing Application Object

...

Accessing Documents and ActiveDocument

From application object one can access document manager, Document Manager has peroperties and Methods by which one can access active document and also can add new document or open You can access the Document Manager from the application object.

The Document Manager provides properties and methods that let you perform the following:

• Access the active document
• Add a new document
• Open existing drawings.

...

Prompting for User

...

Input 

For user IO Editor class is responsible, one can get it from Document and all related class for UserIO are available in The Editor class controls the user input and prints the output into command window. All related classes for prompting on the command window are available in Teigha.EditorInput namespace.

            Document activeDocument = docManager.MdiActiveDocument;
            Editor ed = activeDocument.Editor;

            PromptIntegerOptions op = new PromptIntegerOptions("Input a positive integer");
            op.AllowNegative = false;
            PromptIntegerResult res =(PromptIntegerResult) ed.DoPrompt(op);
            if( res.Status == PromptStatus.OK)
            {
                int retVal = res.Value;
            }

...

.NETExtension Application allow user to run their lets you run your code while loading the plugin. i.e when plugin is loaded it want to add some entries in Ribbon or want to show some UI palatte in ARES Commander then creating the extension application is the right choice. But it is optional and totally depend upon the requirement.To make Plugin as Extension Application one has add a class into project and this class has to implement IExtensionApplication interface and each For example, you can create the Plugin as an Extension Application to display tabs on the Ribbon or palettes while the plugin is loading in the software.

To create the Plugin as an Extension Application, add a class that implements IExtensionApplication interface. Each plugin can have only one class of such this type.

When you load the plugin using the NETLOAD command, the software automatically calls public void Initialize() get called when this plugin loaded via NETLOAD command and Terminate one this plugin unloaded by the System. When the System unloads the plugin, it calls Terminate.

Defining .NET LispFunction

Third party can define .NET methods which is usable that you can use later in LISP, below example defining . The following example defines the lisptest function using the LispFunction Method attribute this funcion is callable by LISP script as .

To call the lisptest function, use the following LISP script:

(setq x (lisptest "Text created by .NET lisp function" 1.0 '(10 10 0)))

...

        //Method attribute to define lisp callable function 'LispTest' 
        //i.e (setq x (lisptest "Text created by .NET lisp function" 1.0 '(10 10 0)))
        [LispFunction("lisptest")]
        public ResultBuffer DoIt(ResultBuffer args)
        {
            // Get the database of the active document.
            Database db = HostApplicationServices.WorkingDatabase;
            TypedValue[] argsVal = new TypedValue[3];
            if (args != null)
            {
                argsVal = args.AsArray();
            }
            else
            {
                argsVal[0] = new TypedValue((int)LispDataType.Text, "Default Text");
                argsVal[1] = new TypedValue((int)LispDataType.Double, .2);
                argsVal[1] = new TypedValue((int)LispDataType.Point3d, new Point3d(0, 0, 0));
            }
            // Set up transaction manager.
            Teigha.DatabaseServices.TransactionManager tm = db.TransactionManager;
            using (Transaction tr = tm.StartTransaction())
            {
                try
                {
                    Point3d pPosition = new Point3d(0, 0, 0);

                    // Create a new MText object and set properties.
                    DBText pText = new DBText();
                    pText.TextString = (String)argsVal[0].Value;
                    pText.Height = Convert.ToDouble(argsVal[1].Value);
                    pText.Position = (Point3d)argsVal[2].Value;

                    // Get model space to add the MText object.
                    BlockTable pBlockTable = (BlockTable)tr.GetObject(db.BlockTableId, OpenMode.ForWrite);
                    BlockTableRecord pModelSpace = (BlockTableRecord)tr.GetObject(pBlockTable[BlockTableRecord.ModelSpace], OpenMode.ForWrite);

                    // Add the object to the model space.
                    ObjectId id = pModelSpace.AppendEntity(pText);
                    tr.AddNewlyCreatedDBObject(pText, true);

                    // Commit changes to database.
                    tr.Commit();
                    //return created text entity to lisp
                    return new ResultBuffer(new TypedValue((int)LispDataType.ObjectId, id));
                }
                finally
                {
                    // delete tr , managed by c# with garbage collection
                }

            }
        }

Migration of AutoCAD® .NET Classic Application to ARES Commander

The .NET applications running on AutoCAD® platform can be easily migrated to ARES Commander by making minimal changes.

• Replace AutoCAD® .NET assemblies by ARES .NET assemblies.
• Replace Autodesk.AutoCAD namespace by Teigha namespace in source code.

Advance Migration

If you don't want to maintain separate source code for AutoCAD and ARES then some extra steps are required, single project with 2 build configuration will solve the issue.

Step 1: Create new build configuration for both AutoCAD and ARES

 Image Removed

Step 2: Using project Properties select all configurations one by one and define Symbol “AutoCAD” or “ARES” for corresponding configurations.

i.e For AutoCAD_Release configuration

 Image Removed

and For ARES_Release

 Image Removed

 Step 3: Add Conditional reference assemblies to the project using Symbols, Modify csproj file manually in text editor to add condition as below for all references.

<ItemGroup>

    <Reference Include="accoremgd" Condition="$(DefineConstants.Contains('AutoCAD'))">

      <HintPath>C:\Program Files\Autodesk\AutoCAD 2018\accoremgd.dll</HintPath>

    </Reference>

    <Reference Include="acdbmgd" Condition="$(DefineConstants.Contains('AutoCAD'))">

      <HintPath>C:\Program Files\Autodesk\AutoCAD 2018\acdbmgd.dll</HintPath>

    </Reference>

    <Reference Include="acmgd" Condition="$(DefineConstants.Contains('AutoCAD'))">

      <HintPath>C:\Program Files\Autodesk\AutoCAD 2018\acmgd.dll</HintPath>

    </Reference>

    <Reference Include="FxCoreMgd_4.03_14" Condition="$(DefineConstants.Contains('ARES'))">

      <HintPath>C:\Program Files\Graebert GmbH\ARES Commander 2018\BIN\FxCoreMgd_4.03_14.dll</HintPath>

    </Reference>

    <Reference Include="TD_Mgd_4.03_14" Condition="$(DefineConstants.Contains('ARES'))">

      <HintPath>C:\Program Files\Graebert GmbH\ARES Commander 2018\BIN\TD_Mgd_4.03_14.dll</HintPath>

    </Reference>

  </ItemGroup>

Step 4: Changes in source code add using directives for both the application conditionally

#if  AutoCAD

using Autodesk.AutoCAD.DatabaseServices;

using Autodesk.AutoCAD.Runtime;

using Autodesk.AutoCAD.Geometry;

using Autodesk.AutoCAD.ApplicationServices;

using Autodesk.AutoCAD.EditorInput;

using CADApp = Autodesk.AutoCAD;

#endif



#if  ARES

using Teigha.DatabaseServices;

using Teigha.Runtime;

using Teigha.Geometry;

using Teigha.ApplicationServices;

using Teigha.EditorInput;

using CADApp = Teigha;

#endif

and Replace Autodesk.AutoCAD to CADApp in *.cs source files which is defined conditional declaration above.

Step 5:

Specify separate Output directories for both the configurations.

Build both configurations one by one these builds will work with their respective applications.

...