Vacation and Multi-Version Revit Add-In Template

As I mentioned in my last post, I am taking lots of time off in July.

This is just a note to let you know I am alive, well and happy, currently in Brassac in Occitanie in southern France ↗, on my way to practice awareness, care and attentiveness in the Buddhist monastery Plum Village ↗ near Bordeaux, founded by the Vietnamese monk and Zen master Thich Nhat Hanh ↗.

On the road, I’ll just share this quick note from a comment by Zhmayev Yaroslav on multi-targeting Revit versions using TargetFrameworks:

Multi-Version Revit Add-In Template

I use .NET SDK and multi-targeting for my NuGet packages all the time and I have to admit that matching different .NET Framework versions to different Revit versions as described in multi-targeting Revit versions using TargetFrameworks is really smart.

All Revit add-in templates I’ve used so far had some small yet really annoying issues, such as:

• They were bloated with author’s information in addin’s manifest (author’s name , vendor id etc.)
• Project dependencies were pointing to files somewhere on template author’s PC
• Debugger tweaked to start Revit.exe from a non-existing location (most of the time it was set to some Revit Copernicus folder or similar, which I assume is the path where Revit beta version is installed or similar)
• You still had to deal with Revit 2017.1.x UI culture bug
• etc.

So, I tried to solve all the problems above and created my own VS2017 Revit add-in template ↗.

It’s a simple “ready to go” template / add-in bootstrap with NuGet dependencies, debugger tweaks for each Revit version, add-in manifest processing etc.

It supports Visual Studio 2017 (15.6+) and 64-bit Revit versions from 2014 all the way up to 2019.

Please try it and let me know if it works for you.

Many thanks to Zhmayev for sharing this!