topic Re: addin version management in Revit API Forum

addin version management

Sherbs — Fri, 28 Jul 2017 13:02:58 GMT

Hi Folks,

Just wondering what some of your "best practices" are for managing add-in development against the various Revit APIs.

As our own projects have migrated from Revit 2014 up through and now including Revit 2018, I'm finding that the way I've been managing code bases is feeling a little clumsy. We've since retired the app with respect to 2014 and 2015, but even supporting our addin against just 3 API versions is tedious.

The way I'm handling things now uses a combination of svn branching/tagging, and svn switching when I need to work on code built against various Revit API versions. My mainline (trunk) code is currently tied to the latest Revit API version that we support, with branches tied to other versions of the API.

This has advantages and disadvantages, as I'm sure other strategies do as well. The two biggest problems I have with the way I'm doing things now are:

1) messy merge - particularly with the .csproj files

2) no obvious indication which branch (or trunk for that matter) is tied to my trunk directory after svn 'switching'.

Just kind of looking for ideas that might work better than what I'm doing. Ideally what I'd like is to have a single VS solution with multiple projects in it - each targeting a different version of the API - but, to have that without having to duplicate any of the add-in code. Try as I might, I've been unable to wrangle VS into a setup like this.

Thanks for any ideas!

Re: addin version management

Anonymous — Fri, 28 Jul 2017 14:05:38 GMT

Have you read this post by Konrad K Sobon?

http://archi-lab.net/how-to-maintain-revit-plug-ins-for-multiple-versions/

Re: addin version management

Sherbs — Fri, 28 Jul 2017 15:13:55 GMT

Aha!

That could be exactly what I've been looking for!

Thanks so much!

-Greg-

Re: addin version management

Dale.Bartlett — Tue, 01 Aug 2017 09:32:43 GMT

I have used this structure. It takes some time and care to set up initially, and you need to constantly compile all versions to be sure older ones are not getting broken with some new code. The suggested link is an excellent guide; the author is to be congratulated. Dale

Re: addin version management

Sherbs — Tue, 01 Aug 2017 13:06:34 GMT

Yep. It worked out perfectly in fact!

I wasn't aware that you could conditionally pull in referenced libraries - that made all the difference.

Accepted as solution.

Re: addin version management

Troy_Gates — Tue, 01 Aug 2017 18:49:37 GMT

Just wanted to add, that in Visual Studio you can batch build your versions (its on the build menu). I use this to build 4 or 5 versions every time I build a project.