2017.2.1 vs 2017

[Dale.Bartlett]

I have some doubts as to the version of the SDK that I should be using for the different flavours and builds of Revit 2017. The last SDK is 2017.1

Can this be used for all versions of Revit 2017? For example:

• Revit 2017
• Revit 2017.2
• Revit 2017.2.1

I have some unexplained errors, and one obvious difference is a mismatch between my development environment (Revit 2017.2, SDK 2017.0, .NET 4.6) and the end-user version (Revit 2017.2.1).  

Many thanks,

Dale

[jeremytammik · Accepted solution]

Dear Dale,

Thank you for your query.

If you think about it for a moment, some things will become clearer.

In what way do you use the SDK to create your application?

I would propose that you do not and cannot use it directly at all to create your add-in in any way whatsoever.

The SDK contains sample code and documentation, nothing else.

The entire Revit API is encapsulated in and provided by the Revit API assemblies living in the same directory as Revit.exe itself.

They are part of the product.

What SDK version you are using has no effect whatsoever on your add-in.

When you compile your add-in, you specify what version of the .NET framework is required.

In Revit 2017 and Revit 2018, it must be 4.5.2 or higher.

I cannot imagine how unexplained errors can be caused by the .NET framework version or the SDK.

One possible source of confusion and errors while compiling an add-in is specifying the wrong path to the Revit API assemblies.

I hope this helps.

Cheers,

Jeremy