The build #0.6 of AutoCAD .Net Addin Wizard (AcadNetAddinWizard) has been rolled out. It has a lot of new features and feature enhancements. It has also addressed some issues and bugs.
It supports Map 3D either old version or the latest 2013 now. Let’s take the C# New Project and Map 3D 2012 as an example here.
Here is the wizard page of product selection.
Here is the option dialog of ‘Assemblies to Reference for the Flavor’.
As can be noticed, it categorized all the Map 3D .NET assemblies into many reasonable groups (and even sub groups for the huge Industry Model, formally called the Topobase, APIs) based on the API features so that programmers can choose to reference the related .NET assemblies into the project with one click. The better part is that if the ‘Add corresponding namespaces to the project’ option is on, the good and proper namespaces of all the checked Map 3D assemblies will be imported into the auto-generated source files as well.
Other wizard pages are more or less the same.
Here are all the namespaces of the AutoCAD, GIS, Map, Geospatial, and Industry Model (Topobase) assemblies as chosen above.
#region Namespaces
using System;
using System.Text;
using System.Linq;
using System.Xml;
using System.Reflection;
using System.ComponentModel;
using System.Collections;
using System.Collections.Generic;
using System.Diagnostics;
using System.Windows;
using System.Windows.Media.Imaging;
using System.Windows.Forms;
using System.Drawing;
using System.IO;
using Autodesk.AutoCAD.ApplicationServices;
using Autodesk.AutoCAD.DatabaseServices;
using Autodesk.AutoCAD.Runtime;
using Autodesk.AutoCAD.EditorInput;
using Autodesk.AutoCAD.Geometry;
using Autodesk.AutoCAD.Windows;
using MgdAcApplication = Autodesk.AutoCAD.ApplicationServices.Application;
using MgdAcDocument = Autodesk.AutoCAD.ApplicationServices.Document;
using AcWindowsNS = Autodesk.AutoCAD.Windows;
using Autodesk.Gis.Map;
using Autodesk.Gis.Map.Annotation;
using Autodesk.Gis.Map.Classification;
using Autodesk.Gis.Map.Constants;
using Autodesk.Gis.Map.DisplayManagement;
using Autodesk.Gis.Map.Filters;
using Autodesk.Gis.Map.ImportExport;
using Autodesk.Gis.Map.MapBook;
using Autodesk.Gis.Map.ObjectData;
using Autodesk.Gis.Map.PE;
using Autodesk.Gis.Map.Project;
using Autodesk.Gis.Map.Query;
using Autodesk.Gis.Map.Topology;
using Autodesk.Gis.Map.Utilities;
using Topobase.AreaTopology;
using OSGeo.MapGuide;
using Topobase.AreaTopology;
using Topobase.AreaTopology.FeatureRules;
using Topobase.AutoCADHelp;
using Topobase.BaseFeatureRules;
using Topobase.Batch;
using Topobase.CER;
using Topobase.Chart;
using Topobase.CIP;
using Topobase.CIP.API;
using Topobase.CIP.Waypoints;
using Topobase.Collections;
using Topobase.CommandRegistry;
using Topobase.CommandRegistry.API;
using Topobase.CommandRegistry.AutoCAD;
using Topobase.Config;
using Topobase.Construct;
using Topobase.CrystalReport;
using Topobase.DataChecker;
using Topobase.Excel;
using Topobase.ExceptionDialog;
using Topobase.Explorer;
using Topobase.FeatureRules;
using Topobase.FeatureSearch;
using Topobase.FeatureServiceListener;
using Topobase.Genuine;
using Topobase.Graphic;
using Topobase.GroupAdmin;
using Topobase.ImageResources;
using Topobase.ImportExport;
using Topobase.Intersection;
using Topobase.JobManager;
using Topobase.JobPerimeterLocator;
using Topobase.License;
using Topobase.Logging;
using Topobase.Management;
using Topobase.Map;
using Topobase.Map.Gws;
using Topobase.Math;
using Topobase.NetworkTracer;
using Topobase.PlaneGeometry;
using Topobase.PlugInHandler;
using Topobase.Profile;
using Topobase.RibbonItems;
using Topobase.Services;
using Topobase.Settings;
using Topobase.SpaceGeometry;
using Topobase.SpatialExportTool;
using Topobase.SpatialQueryService;
using Topobase.SpatialService;
using Topobase.SqlSheet;
using Topobase.TbpReader;
using Topobase.Templates;
using Topobase.Tools;
using Topobase.TopologyExplorer;
using Topobase.TopologyJobsChecker;
using Topobase.Tracing;
using Topobase.Validators;
using Topobase.Workflows;
using Topobase.Exception;
using Topobase.Loader;
using Topobase.TB2TB;
using Topobase.Map.GWS.UI;
using Topobase.Map.GWS.TBExporter;
using Topobase.Map.GWS.WebConfiguration;
using Topobase.Map.Empty;
using Topobase.Map.AutoCAD;
using Topobase.Map.AutoCAD.ContextualTabHelper;
using Topobase.CoordinateSystem;
using Topobase.CoordinateSystem.API;
using Topobase.CoordinateSystem.Factory;
using Topobase.CoordinateSystem.MapGuideApi;
using Topobase.Data;
using Topobase.Data.DAL;
using Topobase.Data.DAL.Oracle;
using Topobase.Data.DAL.SqLite;
using Topobase.Data.DAL.Common;
using Topobase.Data.Provider;
using Topobase.Data.Provider.FDO;
using Topobase.Data.Provider.Common;
using Topobase.Data.Provider.FDO.ADOWrapper;
using Topobase.Data.Provider.FDO.FeatureServiceWrapper;
using Topobase.Data.Provider.FDO.ADOWrapper.Common;
using Topobase.Data.Provider.FDO.ADOWrapper.Data;
using Topobase.Data.Tools;
using Topobase.Data.UnitSupport;
using Topobase.DataModel;
using Topobase.DataModel.Oracle;
using Topobase.DataModel.SqLite;
using Topobase.DataModel.SystemUser;
using Topobase.DataModel.DocumentUser;
using Topobase.Display;
using Topobase.Display.DisplayModelManagement;
using Topobase.Display.GraphicsGeneration;
using Topobase.Display.GUI;
using Topobase.Display.LoadOnOpen;
using Topobase.Display.ResourceManager;
using Topobase.Display.Settings;
using Topobase.Display.Web;
using Topobase.Exchange;
using Topobase.Exchange.CoordinateFiles;
using Topobase.Exchange.XmlSpy2008Schema;
using Topobase.Exchange.XmlSpy2008SchemaXML;
using Topobase.Forms;
using Topobase.Forms.Basis;
using Topobase.Forms.Designer;
using Topobase.Forms.Desktop;
using Topobase.Forms.Desktop.Controls;
using Topobase.Forms.Manager;
using Topobase.Forms.Remote;
using Topobase.Forms.Report;
using Topobase.Forms.SqlTreeView;
using Topobase.Forms.UserControls;
using Topobase.Forms.Utils;
using Topobase.Forms.WpfControls;
using Topobase.GeometryConverter;
using Topobase.GeometryConverter.API;
using Topobase.GeometryConverter.AutoCAD;
using Topobase.GeometryConverter.Factory;
using Topobase.GeometryConverter.Fdo;
using Topobase.GeometryConverter.Gml;
using Topobase.GeometryConverter.MapGuidePlatform;
using Topobase.LogicalTopology;
using Topobase.LogicalTopology.FeatureRules;
using Topobase.ManagedLeda;
using Topobase.ManagedLeda.SpatialServiceImpl;
using Topobase.Modules;
using Topobase.Modules.Common;
using Topobase.Modules.Electric;
using Topobase.Modules.Electric.Common;
using Topobase.Modules.ElectricCE;
using Topobase.Modules.ElectricNA;
using Topobase.Modules.Gas;
using Topobase.Modules.Survey;
using Topobase.Modules.Survey.API;
using Topobase.Modules.Survey.Import;
using Topobase.Modules.Survey.ImportAPI;
using Topobase.Modules.Survey.Client;
using Topobase.Modules.Survey.PointCalculation;
using Topobase.Modules.Survey.PointCalculation.Matrices;
using Topobase.Modules.WasteWater;
using Topobase.Modules.WasteWater.API;
using Topobase.Modules.Water;
using Topobase.Plot;
using Topobase.Plot.Api;
using Topobase.Plot.Application;
using Topobase.Plot.Components;
using Topobase.Plot.Data;
using Topobase.Plot.Forms;
using Topobase.Report;
using Topobase.Report.CrystalReports10;
using Topobase.Report.Default;
using Topobase.Reports;
using Topobase.Reports.SurfaceDefinition;
using Topobase.Schematics.Core;
using Topobase.Schematics;
using Topobase.Schematics.UI;
using Topobase.Update;
using Topobase.Update.Forms;
using Topobase.Update.Xml;
using Topobase.Update.Properties;
using Topobase.Util;
using Topobase.Utilities;
using Topobase.Utilities.App;
using Topobase.Utilities.Properties;
#endregion
As can be seen, there are almost two hundred namespaces in total. Here they are all imported into the source files automatically and nicely.
The following image shows the assembly references in the project.
Because of the length of the window, only some of the Topobase assemblies are shown here. There are much more. Imaging how much time it would take and how boring it would be to add all these references into the project manually and import all related namespaces into those different sources.
With the AutoCAD .NET Addin Wizard (AcadNetAddinWizard), only a few clicks are necessary. It will still take a few minutes to bring all the references in though in that it’s also a relatively complex and time consuming process for the Visual Studio IDE itself. Users can take this chance to leave the computer for a while and cook a cup of instant coffee or tea to enjoy.
Enjoy both the wizard and the coffee/tea!
The leading edge AutoCAD .NET Addin Wizard (AcadNetAddinWizard) provides various project wizards, item wizards, coders to help program AutoCAD .NET addins.
Posted by: |