-
Notifications
You must be signed in to change notification settings - Fork 13
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
Revit 2025: FileLoadException - could not load file Nice3Point.Revit.Toolkit #11
Comments
can you ensure that you don't implement Revit Api IexternalCommand and IexternalApp ? |
I have one instance of The only "IExt..." in the project is |
also, it works fine with Revit 2024 |
A known problem on Revit 2025, the issue is that Revit doesn't want to load a dependency that is a higher version than the one already loaded. A temporary solution is to run DependenciesReport jeremytammik/RevitLookup#269 (comment) to find a plugin with an older version and copy Toolkit version 2025.0.3 to it |
Does this mean that Nice3point/RevitToolkit should not be used with Revit 2025 unless the temporary solution is used?
Could you explain in more detail what this means? What older version of which plugin would resolve this? |
you can, why not, you just need to update the plugins that use RevitToolkit with older versions, like 2025.0.1
Can you run DependenciesReport from the link above and send the generated report here so we can figure out the cause of the problem? |
@harrymattison Update please RevitLookup to the 2025.0.10 version |
Thanks, but how can I publish a product that will fail to load based on the version of some other product? |
Toolkit gives more conflict protection than not using it at all. There are always chances to encounter incompatible plugins, Autodesk solves this problem, so we can only hope that they will do something in Revit 2026. |
Hi Roman - I am getting this error when starting Revit 2025
But that DLL does exist in the folder with the add-in dll
CSPROJ.txt
Is there some other file that needs to be included? Thanks
The text was updated successfully, but these errors were encountered: