Revit 2027 add-in migration to .NET 10
Autodesk® Revit® 2027 software runs on .NET 10 and loads all-user add-ins from a new folder. If your team relies on in-house or inherited add-ins, we review the code for free, then move them to Revit 2027 for a fixed price, without breaking the versions you still run.
Four changes that stop old add-ins from loading.
These come from the Revit 2027 SDK notes. Each one can turn a working tool into a missing ribbon button on upgrade day.
.NET 10 runtime
"Revit 2027 now runs on .NET 10", and add-ins must be built against the .NET 10 SDK. Libraries your add-in ships with may need updating too.
New install folder
Revit 2027 "no longer looks for machine-wide add-ins under ProgramData". All-user add-ins now go under C:\Program Files\Autodesk\Revit\Addins\2027. Per-user installs still work.
Dependency isolation
New manifest settings (Dependencies, PublicAssemblies) control which add-ins share libraries. Add-ins that relied on another add-in loading first may need an explicit dependency.
Removed and changed API
Hard-coded cloud regions, some Mechanical.Zone members, legacy rebar creation methods and some energy settings were removed or replaced. Code that calls them won't build.
Sources: Autodesk Developer Blog, Revit 2027 SDK: .NET 10, API changes and additions, Apr 10, 2026; Revit API forum, Revit 2027 add-in installation folder changes.
One add-in, up to three builds.
You can't retarget everything to .NET 10: a .NET 10 build won't load in a Revit update that still runs .NET 8. We keep one source code base and produce the builds each version needs.
| Revit version | Runtime | Build we ship |
|---|---|---|
| 2024 (2023 on request) | .NET Framework 4.8 | net48 build |
| 2025.0–2025.4, 2026.0–2026.4 | .NET 8 | .NET 8 build |
| 2025.5+ and 2026.5+ | .NET 10 runtime | The same .NET 8 build, which Autodesk expects to load but doesn't guarantee, so we test on both |
| 2027 | .NET 10 | .NET 10 build, installed to Program Files or per user |
Microsoft ends .NET 8 support in November 2026. See our .NET 8 article for what that means day to day.
Review free, then a fixed price.
Free code review
You share the source under NDA. We list every add-in, the Revit versions it must run on, the libraries it ships, and the API calls that changed.
about 3 business daysWritten scope and price
A fixed price per add-in or for the whole set, the builds you'll get, and a written acceptance test on your Revit versions.
within 2 business days of the callMigrate and test
One code base, multi-target builds, updated manifests and installers. Tested on sample models and a copy of yours, on each Revit version and update you name.
estimated 1–4 weeksHand over
Installers, full source, a build guide and a version matrix. 30-day bug-fix warranty after acceptance.
on acceptance
What you get
- Builds for Revit 2024 to 2027 from one source code base
- Updated
.addinmanifests, including Revit 2027 dependency settings where needed - Installer for the new Program Files location, or a per-user install that needs no admin rights
- Replaced calls to removed API members
- Updated third-party libraries, with license notes
- Full source code and a short build guide
Good to know
- Prices are quoted after the free code review, because the work depends on the code.
- We migrate what you have. New features are scoped separately.
- If there's no source code, tell us on the call. Rebuilding a tool from its behavior is a new build, not a migration.
- Dynamo graphs moving to Dynamo 4.0 and PythonNet3 are covered on the Dynamo & pyRevit page.
Revit 2027 migration FAQ
Our add-ins still work in Revit 2026. Do we need to do anything now?
Not on the day .NET 8 support ends, but plan before you roll out Revit 2027 or the 2025.5 and 2026.5 updates. Test every add-in on each version and update your team runs, starting with tools that have windows or ship their own libraries.
Can you migrate an add-in someone else wrote?
Yes, if you have the source code and the right to change it. The free code review tells you how much work it is before you commit.
Will the migrated add-in still run on Revit 2024?
Yes. We build from one code base for each runtime, so the versions you still use keep working.
Who owns the migrated code?
Work made only for you is assigned to you in writing once paid in full. See Security & IP.
Have a Revit task your team repeats every week?
Tell us about it. Within 2 business days of the call you get a written scope with a fixed price for a pilot or first phase, and an estimate range for anything bigger. No obligation.