API Versions

[GuyR]

Can anyone answer this.

Is the API backward compatible? Or should we release a version for each Revit version.

Guy

[Danny Polkinhorn]

The API appears backwards compatable as long as you don't use methods that only exist in 8.1 (obviously). I think in the future you'll be able to tell what version (and vertical) you're dealing with so you can adjust your code accordingly.

[FK]

Generally, expect to release a fresh build of your plugin for each version of Revit. This is very likely with the weak versioning support of COM, maybe not necessarily so with .net, I'm not sure.

Rebuilding is not a very big deal, especially once you've scripted the whole process. So the question is how much compatibility there is between versions - how much code you have to touch to make sure your application still works correctly.

Obviously, your plugin will fail if it tries to use features that are not implemented in the version you are using. So, this kind of backward compatibility is out of question.

But, of course, you want forward compatibility. You wish the API didn't change or Revit upgraded your code like it upgrades a project. Well, the API may change, and you may have to modify things. But there are capable developers in charge, feeling your pain. We try to look ahead and minimize painful changes. I don't think we broke forward compatibility over the two versions, but we will try to document what's going on.

[GuyR]

Cheers Fedor,

or Revit upgraded your code like it upgrades a project.

I like this idea. If Revit could write the code that would be perfect I don't have a problem releasing multiple versions or upgrading. It was really just a question of how .NET works the API when there are multiple versions of Revit installed.

but we will try to document what's going on.

A what's changed document would be really useful.

Guy