Using Revit API 2024 in Revit 2025

[otto_lagerquist]

Hi!

Currently I'm developing an adding for Revit 2024 using the Revit API 2024. Now we are starting to also use Revit 2025 for new projects, and of course we'd like the addin to be available in these projects too. I've read a lot about the process of migrating from .Net Framework 4.8 to .Net Core 8.0 but I'm feeling lost when it comes to handling and developing multiple versions side by side (potentially due to me beeing relatively new in software engineering). To me it seems like it will lead to double the amount of work...

Would it be possible to keep using the addin for Revit 2024, using Framework 4.8, in Revit 2025 as long as I'm sticking to the features available in the 2024 API? I have done some initial testing and it seems to work fine loading the addin and using the commands, but I haven't yet tested enough to know if it will break in certain special situations.

In this case my plan would be to stick with this version until we're not continuously adding features and then do a one time upgrade, and continue developing the .Net core 8 version only in the future.

Would be happy for any thoughts or guidance on the matter.

Thanks

[ricaun · Accepted solution]

By default is a good practice to build one dll for each version of Revit using the respected Revit API references. The IDE gonna show what features the API have and the Obsolete that could be remove in the future versions of the api, so you can prepare you code before the feature is removed.

If you have a plugin design to run in Revit 2024 with Framework 4.8 and runs and works in Revit 2025 that uses Net Core 8.0. You are lucky 😀

I have a demo plugin that runs in Revit 2025 using the Revit 2024 dll, is kinda a simple plugin and don't use any references related to the Net Framework. I still gonna create a new version to build the project using the Net Core 8.0 and the Revit API 2025, it's easier to maintain if you design and build the plugin in the correct version.

---

@otto_lagerquist wrote:

In this case my plan would be to stick with this version until we're not continuously adding features and then do a one time upgrade, and continue developing the .Net core 8 version only in the future.

---

You should update and learn how to create a plugins to build for version 2024 and 2025. Today you don't have the time pressure, your plugin is already working, but in the next version of Revit how knows if gonna work or not.

And if you already have your project prepared to build for version 2024 and 2025, gonna be really easy to make work in the next version.

I use the Configuration way to build each version of Revit, each configuration has one Revit version, 2021, 2022, 2023, 2024, 2025.

Sometimes I don't have in the project similar versions that share similar FrameworkVersion like the 2022, 2023 and 2024 could work with the dll for the version 2021.

Version 2025 uses Net Core and could require different dependencies design for Net Core, so a configuration for that.

Here is a project that use this setup.

https://github.com/ricaun-io/RevitAddin.FamilyLoader/blob/develop/RevitAddin.FamilyLoader/RevitAddin...

[CollinJoseph0258]

Thanks for sharing that project Luiz. 

I have been working on configurations for multiple Revit versions as well and this was VERY helpful. 

😀

[otto_lagerquist]

Thanks @ricaun for your helpful answer! I've had a look at your project and will try to make a setup like that work.