Attention Revit Add-in Developers!
Autodesk is planning to migrate Revit 2025 and 2026 to .NET 10. We need your help test your application against Revit on .NET 10.
Revit 2025 and 2026 are built on .NET 8. As many of you are aware, Microsoft is ending support for .NET 8 on November 10, 2026. .NET 10 is Microsoft’s latest version of long-term support (LTS) release. Autodesk plans to follow Microsoft’s LTS and migrate the previous two versions of Revit to .NET 10. Adapting the newer, modern version of .NET may provide benefits such as enhanced performance, enhanced security, ongoing platform support, and access to newer runtime and tooling capabilities. It also helps strengthen the foundations that Revit and the Revit ecosystem rely on, including better runtime efficiency and more modern language features.
From our experience so far, most add-ins continue to work. However, if your add-in is built using a complex environment, e.g., using native code and third-party libraries, results may vary. There may be cases where recompilation and dependency updates are required. We would like to know about such cases so we can help to minimize disruption to our developers and customers where possible. It is important that Revit add-in developers test your applications and report issues to us as soon as possible.
Action Required
Autodesk has provided a preview version of Revit 2026 with .NET 10 on April 28. It is accessible through the existing Revit Preview feedback portal. If you have a Revit add-in that runs on Revit 2026*1, please visit the Revit Preview portal and start testing your application against the .NET 10 version of the build. The testing/feedback period will continue till June 3rd.
More detailed technical information about .NET 10 migration is available on the Revit Preview feedback site.
*1) Revit 2025 is expected to be made available at later date, after Revit 2026; timing is subject to change.
References:
Leave a Reply