Microsoft ends support for .NET 8 and .NET 9 on November 10, 2026, and Autodesk has been moving its 2025 and 2026 desktop releases, Revit included, to .NET 10 ahead of that date. For Revit users and add-in developers still on these versions, now is the time to confirm that updates are installed and that plugins load correctly.
What’s new
According to the Autodesk Developer Blog, Revit 2026.5 is the update that brings the 2026 release onto .NET 10. Autodesk targeted the first week of August 2026 for it, and an August 18 edit to the post states that all Autodesk 2026 products covered by the plan have been released. The Revit 2025 line followed through a Revit 2025.5 preview, with general availability planned for the second week of September 2026.
- Other products in the same transition include AutoCAD 2026.1.2 and its verticals (Civil 3D, Advance Steel), Inventor 2026.4 and Vault 2026.4.
- Autodesk advises installing updates for all Autodesk products of the same release year together.
- For developers, Autodesk states “There are no API changes” in these updates.
- Existing add-ins should keep working, unless they are affected by .NET 10 breaking changes. Those need to be recompiled and retargeted to .NET 10.
Revit 2027 already ships on .NET 10, as covered in the Revit 2027 SDK notes, so this transition concerns the two previous releases.
Why it matters
Many offices still run Revit 2025 and 2026 on live projects. Once .NET 8 is out of support, staying on an older update means relying on a runtime that no longer receives Microsoft security fixes. BIM managers should check which Revit update is deployed on each workstation and plan a coordinated rollout, since Autodesk recommends updating products of the same year together.
Developers and in-house tool teams should test their add-ins on Revit 2026.5 and the 2025 .NET 10 update, especially tools that bundle third-party libraries. Autodesk notes that release timings could change, so confirm the exact update available in your Autodesk Account before deploying.
Source
Read the original announcement: Autodesk Developer Blog
