http://www.charlesandhudson.com/archives/hand-tools-list-important.jpgPPT_LOGO_4b
‹#›
Autodesk Developer Network, April 2010
The Rice – Changes to Revit API Namespaces
•Revit 2011 divides the API three primary namespaces:
•Autodesk.Revit.ApplicationServices
§Classes accessing application settings and options
•Autodesk.Revit.DB
§Classes accessing file data
•Autodesk.Revit.UI
§Classes accessing or customizing the user interface
C:\Documents and Settings\walmslk\Local Settings\Temporary Internet Files\Content.IE5\EARWAUQM\MPj04096740000[1].jpg
The namespaces have undergone considerable re-structuring to enable
1)Quicker and structured access to API functionality that the API users need to work with. Getting access to the right functions was one of the reasons
2)There was no way to scale up the API without some fundamental reorganization of structure which would help it expand not just now but in releases to come
3)There was a need to separate the UI from the DB more cleanly. There were also some requirements to separate the Revit engine from the UI and more work on this was done which is now manifesting itself through the API.

In previous releases, the API was split along the functionality around the verticals which led to confusion about where the classes were if elements or symbols were specific to one vertical.

So now we have three main namespaces –
1)Application Services – Similar to AutoCAD’s ApplicationServices namespaces.
2)DB – classes accessing the file data
3)UI – classes accessing or customizing the UI