Upgrading your API applications to a new Revit version – Part 2

How to set up conditional compilation and conditional references to different DLL versions so your API program can simultaneously support Revit 2013, 2014, and 2015.

Advertisements

6 thoughts on “Upgrading your API applications to a new Revit version – Part 2

    • I just started updating my addins using this great method, thanks again for the info.

      I wanted to note that I also found that you can add the configuration to the Build Events like so:

      if $(ConfigurationName) == 2014 copy “$(ProjectDir)bin\2014\some.dll” “$(AppData)\Autodesk\REVIT\Addins\2014”
      if $(ConfigurationName) == 2015 copy “$(ProjectDir)bin\2014\some.dll” “$(AppData)\Autodesk\REVIT\Addins\2015”

  1. Hello Harry

    thanks for posting this, however, I believe it is better to wrap the revit version dependant code in calls to dependant dll’s (C#projects). This means you don’t have to create multiple builds (and configurations) for multiple versions of Revit. Thus the same addin can be used in multiple revit versions.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s