PPT_LOGO_4b
‹#›
© 2008 Autodesk
Autodesk Developer Network
Resolving Naming Ambiguities
§At the beginning of each file:
§
§
§
§
§
§
§
§
§
§
§
§In VB, pure Imports can be defined via properties on project level, but not Imports xxx = yyy.zzz statements
Imports System.Windows.Forms
' ...
' AutoCAD
Imports Autodesk.AutoCAD.DatabaseServices
' ...
' ACA (Aec)
Imports Autodesk.Aec.DatabaseServices
' ...
' To resolve Object/Entity ambiguities
Imports AcObject = Autodesk.AutoCAD.DatabaseServices.DBObject
Imports AecObject = Autodesk.Aec.DatabaseServices.DBObject
Imports AcEntity = Autodesk.AutoCAD.DatabaseServices.Entity
Imports AecEntity = Autodesk.Aec.DatabaseServices.Entity
' To resolve Application ambiguities with System.Windows.Forms
Imports AcadApp = Autodesk.AutoCAD.ApplicationServices.Application
There are some ambiguities between AutoCAD.NET and ACA.NET class names, for instance DBObject and Entity are available in several different namespaces. These can be easily resolved where needed using aliases.