Revit 2011 Product GUIDs

We discussed issues related to the

Revit install path and the product GUIDs for
versions up to and including Revit 2010 last year.
The install path is less of an issue nowadays, since there is no longer a need to determine the location of Revit.ini to install an add-in, because you can use an add-in manifest file instead.
Another more exciting reason is the availability of the new

add-in utility DLL
described below.
Still, the product GUID may be important for many other uses, so here is the updated list including the GUIDs for the Revit 2011 versions:

td.j311
{
border-color: darkgrey;
border-width: 1px;
border-style: solid;
}

ADN members may also refer to the technical solution

TS87598 [How to detect where Revit has been installed?]

RevitAddinUtility

In the past, the Revit product GUIDs were often used to determine the Revit installation location.
In Revit 2011, this can be achieved a lot simpler and safer by making use of the new RevitAddinUtility functionality.

RevitAddInUtility.dll is a new .NET utility class assembly which lives in the Revit Program folder, in the same location as Revit.exe, Revit.ini, and the Revit API DLLs.

The Revit SDK provides documentation on how to use it in its own little help file RevitAddInUtility.chm, as well as a sample application RevitAddInUtilitySample demonstrating its use.

The latter is located in the ExternalCommand2011 folder, which contains two separate very interesting sample applications:

• RevitAddInUtilitySample
• ExternalComandRegistration

Here is an excerpt from the documentation of these two in ‘ReadMe_ExternalCommand 2011.docx’:

Two samples with the following functionality demonstrate how to use the new external command registration more effectively:

• RevitAddInUtilitySample: Show how to use RevitAddInUtility to create and edit an add-in manifest file, retrieve information from the manifest file, and retrieve installed Revit product information.
• New features of external command registration:
  1. Visibility mode: demonstrate how to control the visibility of each external command based on the different product and document types.
  2. IAvailabilityClass: demonstrate how to dynamically enable or disable individual external commands bases on the current user’s selection or other application information.
  3. Icon and tooltip: demonstrate how to define an external command’s ribbon icon and tooltip.
  4. Localization: demonstrate how to localise strings in the add-in manifest file.

Enthusiasm and Namespaces

Guy Robinson gives vent to some

enthusiasm about
Revit 2011 and the new API
and provides a lot of interesting background information on and a pointer to a powerful tool for handling the

namespace refactoring in
the Revit 2011 API, which might save a significant amount of porting time and effort.

Revit 2011 API News Webcast

Kean Walmsley points out that we have yet another group of events that I forgot to mention on Sunday besides the

DevCamp, Devlabs and API training classes:

free online sessions on the 2011 products and their APIs.
The session on what’s new in the Revit 2011 API is taking place on April 21^st, and once again you can visit our

training schedule (also accessible via

autodesk.com/apitraining > Schedule) to attend.
He also points to some other product related sessions that may be interesting to you.