This project was generated by the ricaun.AppLoader Revit plugin.
In Revit 2026 the feature Option for Add-in Dependency Isolation was introduced, which allows add-ins to be loaded in an isolated context.
The problem is there a internal implementation that share the assembly even if is in a different context, this makes the isolation ineffective.
There is another specific problem with this Resolver pointing to the assembly in a different context, which this project is design to reproduce.
If the assembly is loaded in a collectible context, and the Resolver selects that assembly to use in the Default or non-collectible context.
The exception NotSupportedException: A non-collectible assembly may not reference a collectible assembly. happens and the addin fail to load the assembly dependencie.
This issue only happens in Revit 2026 that has this shared assembly context implementation.
These are the related threads in the Revit API Forum:
- Context Isolation in Revit 2026
- Revit 2027 ManifestSettings deduplication mechanism (from Revit 2026) missing?
- Install
bundleusing the installer RevitAddin.CollectibleContext2026.exe
Or using AppBundleTool with the following command:
AppBundleTool -a https://github.com/ricaun-io/RevitAddin.CollectibleContext2026/releases/latest/download/RevitAddin.CollectibleContext2026.bundle.zip -iThis project is licensed under the MIT License.
Do you like this project? Please star this project on GitHub!