Revit API Training Preparation

Yesterday I pointed out that the

Revit 2012 API training material
is
now available online from the
Revit Developer Center and
provided a more or less detailed overview of its content.

In addition to downloading and working through that, there are a couple of other preparations that I recommend my training participants to work through up front:

The SDK, DevTV classes, and first plugin tutorial are all available from the
Revit Developer Center.

RevitLookup, RvtSamples, and the developer guide are part of the SDK, and the developer guide is also
available online.

Whether you work through the developer guide hands-on walk-throughs, the DevTV classes or the ‘first plugin’ material first is up to you.
The content covered overlaps to some extent.

If you like, you can postpone the installation of the SDK until after you have worked through these.
Working through them first will deepen your understanding of the installation of Revit add-ins, which will be useful for setting up RevitLookup and RvtSamples.

Once you have done all or most of this, you will be in a good shape to work through the

Revit 2012 API training material
,
which provides a pretty thorough introduction to all the basics of the Revit API.

Everything beyond goes into more depth in specific areas of your interest, either related to the particular Revit flavour appropriate to your domain or specialised advanced areas within the Revit API.

Here are a few more notes on the installation of the SDK, RevitLookup and RvtSamples:

Installing the SDK is trivial; it is an executable file, so you run it and specify a location of your choice to place the contents into.

To install

RevitLookup
(formerly
RvtMgdDbg, described

here
in detail),
you open the Visual Studio project in the RevitLookup subfolder of the SDK installation folder, compile it, edit the add-in manifest file to point to the correct assembly location specifying the path of your add-in DLL, and copy that to the

appropriate


location
(replace ‘2011’ by ‘2012’) for Revit to pick up.

RvtSamples provides an interface to load and run all of the hundred-plus other SDK samples, instead of installing them individually.
Therefore, it requires you to compile all the other SDK samples as well, as described in the following posts:

I hope that this information is complete enough to get anybody interested in the Revit API happily started.
Please let me know if you discover anything missing.


Comments

5 responses to “Revit API Training Preparation”

  1. Hey, Jemery:
    I tried to use Autodesk.Revit.Geometry.Element in my project. But it shows me the following message “type or namespace name ‘Geometry’ does not exist in the namespace ‘Autodesk.Revit’ (are you missing an assembly reference?)
    Should I add more reference library or anything else I need to do?
    Thanks very much.
    Rui Liu

  2. I mean ” do I miss a reference”? Sorry about that :)

  3. Good blog..and its very interesting also.. Should I add more reference library or anything else I need to do..keep sending like this good blog..its really use to us..

  4. Dear Rui Liu,
    Nope, you do not need any other than the two references to RevitAPI.dll and RevitAPIUI.dll in order to obtain access to the full Revit API.
    The namespace Autodesk.Revit.Geometry was provided in the Revit 2010 API, though, and is obsolete now.
    In Revit 2011 and 2012 the geometry elements were moved into the namespace Autodesk.Revit.DB.
    You need to change the code to use that namespace instead.
    An easy way to create all the required ‘using’ statements automatically through Visual Studio Intellisense is using the Ctrl-‘.’ keystroke combination described in
    http://thebuildingcoder.typepad.com/blog/2010/07/linq-methods-and-visual-studio-tips.html#2
    Cheers, Jeremy.

  5. Dear Rui Liu,
    No worries, mate.
    Cheers, Jeremy.

Leave a Reply

Discover more from Autodesk Developer Blog

Subscribe now to keep reading and get access to the full archive.

Continue reading