Error loading package

[john_pierson]

note, my examples below are for Revit, but the ideas should hold true for Civil3d

@mzjensen

Are the only solutions for this to use late binding or build separate package versions for each version of the host app?

The only solution I have seen similar to that is how archilab is released and that creates a ton of issues if you are managing deployments for anyone on multiple versions of the host software.

---

For my package Rhythm, I elected to separate functionality for later versions and use invoke to fire the commands off right from the DLL. This means the dependencies (for Revit 2022 in my case) don;t actually get referenced in older Revit versions.

Here is sample code:

The Rhythm Revit 2022 code (which becomes its own DLL RhythmRevit2022.dll in the extra folder):

johnpierson/RhythmForDynamo/blob/871531a5c8855de22967da4ecd5b7012ec6393ee/src/RhythmRevit2022/Revit/Elements/Viewport.cs#L16-L24

and the actual ZeroTouch code that calls it (in my base Rhythm.dll):

johnpierson/RhythmForDynamo/blob/871531a5c8855de22967da4ecd5b7012ec6393ee/src/Rhythm/Revit/Elements/Viewport.cs#L321-L330

and the invocation utilities: https://github.com/johnpierson/RhythmForDynamo/blob/master/src/Rhythm/Utilities/Utilities.cs