Quick Links - Also see the menu above and more choices on the right side of the blog (too much, but all good stuff)

\/ ...and now BIMbuilder.com Blog Posts... \/

Wednesday, March 28, 2012

The Building Coder: Revit 2013 and its API

Source/Link:  The Building Coder: Revit 2013 and its API


Revit API Enhancements

Looking at the enhancements provided in the new Revit API affecting existing add-ins, the effort required to migrate an existing add-in from the previous version is pretty minimal this time around. As always, efforts were made to change as little as possible and still keep up momentum. Add-ins must now be built using the .NET 4.0 framework, old-style collections have been replaced by generic .NET collections, the wall creation methods have been updated, the Document.Element properties have been better aligned with standard .NET conventions, and deprecated APIs have been cleaned up.
An area that does not affect add-ins but may still be of interest to developers is the replacement of the VSTA macro environment by the open source SharpDevelop IDE, which offers all the existing functionality plus some new features such as support for .NET 4.0.
A new ReferenceIntersector class simplifies the use of the FindReferencesWithContextByDirection method, the Idling event has been enhanced, and a new external event interface is defined to simplify interaction with external asynchronous processes, such as modeless dialogues.

Revit API New Features

A lot of completely new API functionalities are provided in this release. It can be grouped in many different ways. I will group them them into these five containers:


One large goal encompassing many developer wish list items is the improvement of the user experience when using an add-in. This topic includes features that allow add-ins to integrate better into the Revit UI, and even vice versa, integrating a little piece of Revit functionality into an add-in by hosting a Revit view:
  • Discipline control to read and set the discipline status and control the disciplines under which an add-in's command is available.
  • Ribbon items can now provide contextual help, so the user can simply hit F1 on an add-in command button to bring up an Internet URL or a local help file entry.
  • API commands can be assigned keyboard shortcuts.
  • API commands can be moved to the quick access toolbar.
  • An add-in can replace an existing Revit command with its own implementation. Note that you cannot call an existing command, just replace it entirely. This functionality is also used by Autodesk’s own add-ins to extend commands, e.g. the Render Gallery.
  • An add-in can embed a Revit view as WPF control inside its own dialogue for preview purposes, also supporting rendered views. An add-in can create a view showing exactly what needs to be communicated to the user and display this graphically.
Revit view in WPF control

    ...Continue reading, there's a lot more and I don't understand a word of it.
     The Building Coder: Revit 2013 and its API


    • buildingSMART alliance Florida BIMSMART Summit 3/29/12 in Fort Lauderdale - Register
    • Are you getting your CM-BIM credential? Click here for classes and information
    • Click here to Subscribe to the blog via daily email updates for the BIM news you don't want to miss.


      © Blogger template ProBlogger Template by Ourblogtemplates.com 2008

    Back to TOP  

    [Valid Atom 1.0]