-
Notifications
You must be signed in to change notification settings - Fork 0
Hosts Revit
Truong Giang Vu edited this page May 31, 2026
·
1 revision
Revit is the main supported RevitDevTool v3.0 experience.
The current build matrix supports Autodesk/Revit configurations from 2022 through 2027:
| Revit version | Target framework |
|---|---|
| 2022-2024 | net48 |
| 2025-2026 | net8.0-windows |
| 2027 | net10.0-windows |
- run Python scripts that call the Revit API;
- install Python dependencies from script metadata;
- debug Python in VSCode;
- run compiled Revit add-ins;
- run C#
.csx, F#.fsx, and IronPython scripts; - inspect logs and Python stack traces;
- visualize temporary Revit geometry;
- expose selected tools through MCP;
- run pytest-style checks that need Revit context;
- search and run commands through Command Browser;
- watch memory usage when diagnosing heavy scripts.
| Use case | Recommended page |
|---|---|
| Quick Python automation | Modern Python Scripting |
| Revit API add-in development | .NET Assembly Execution |
| Fast C# or F# experiment | Scripting Runtimes |
| Visual geometry debugging | Visualization Overview |
| AI-assisted tool access | AI Tool Integration |
| Tests that need Revit API context | PyTest Bridge |
Revit API calls must run in a valid Revit API context. Scripts launched through RevitDevTool are designed for that. Modeless UI or background work still needs to marshal Revit API calls back through the provided Revit execution path.
Visualization is currently a Revit DirectContext3D feature. Geometry traced or printed by scripts can be shown temporarily in the active view without creating model elements.
Supported geometry categories include:
- XYZ/points
- curves and polylines
- bounding boxes/outlines
- meshes
- faces
- solids
- planes
- Revit API behavior cannot be fully validated by pure unit tests.
- Some workflows need a live Revit session.
- Geometry visualization is tied to active Revit view/rendering state.
-
net48compatibility still matters for Revit 2022-2024. - Python/IronPython behavior depends on installed runtimes and enterprise machine restrictions.
- Run Code Overview
- Modern Python Scripting
- Python Debugging
- Python Ecosystems
- RevitDevTool And pyRevit
- Python Stub Generation
- Run .NET Add-ins
- Scripting Runtimes