-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency conflict with third-party plugins #269
Comments
DependenciesReportThis tool designed for static analysis of dependency conflicts between plugins. Displays a conflict summary and optionally updates dependencies to the latest version. It works without starting Revit. Download:
Source code: https://github.com/jeremytammik/RevitLookup/tree/dev/tools/source/DependenciesReport If you have problems with running RevitLookup, please send reports: Be careful when running the upgrade, dependencies that are not backwards compatible may break older plugins: AssembliesReportThis tool designed for Revit, creates a report on the dependencies used. Aimed at helping to trace the loading of dependencies. Download:
Source code: https://github.com/jeremytammik/RevitLookup/tree/dev/tools/source/AssembliesReport
|
@acco-jpitts at the moment Revit Toolkit is the only one bottleneck that can cause failures in Revit 2025, as it is this library that provides isolation. I will look into how to get around this, thanks for the clarification |
@Nice3point Please have a look, there have conflict between Python node in Dynamo and RevitLookup
|
Native add-in isolation planned for feature Revit updates |
Interesting! Where did you get this file? Edited: |
RevitLookup uses third-party dependencies produced by other developers. User plugins may also use these dependencies, but of different versions, which will cause a conflict and an exception on startup. We have no control over this process, and we cannot prevent other developers from using third-party libraries.
Why are you getting this error in RevitLookup and not in another plugin? Because plugins are loaded in alphabetical order, and the 'R' is near the end, so that's where you get the exception and RevitLookup not working. Unfortunately, the plugin that is loaded first forces Revit to use it dependencies for all plugins. And if it's outdated, RevitLookup, which uses the newest one, will simply be incompatible, if everything was in reverse order this could have been avoided.
At the moment there are some ways, disable conflicting plugins:
_RevitLookup.addin
. Add-ins are loaded in alphabetic order.Remember though, you can fix RevitLookup in this way, but there is a chance that conflicting plugins may not work.
RevitLookup dependencies list:
https://github.com/jeremytammik/RevitLookup/blob/dev/source/RevitLookup/RevitLookup.csproj#L45-L71
The text was updated successfully, but these errors were encountered: