-
Notifications
You must be signed in to change notification settings - Fork 0
Getting Started Install
Truong Giang Vu edited this page May 31, 2026
·
1 revision
- Download the latest installer from GitHub Releases.
- Run the MSI installer.
- Start the target Autodesk host.
- Open the RevitDevTool or DevTools panel from the host UI.
Typical workflow (applies to both Revit and AutoCAD-family hosts):
- Open the RevitDevTool dockable panel.
- Add script folders or assembly folders in settings.
- Pick a discovered command.
- Run it.
- Inspect trace output, log output, and optional geometry visualization.
The shared script provider discovers script entry files by suffix:
| Script type | Entry suffix |
|---|---|
| CPython | *script.py |
| IronPython | *_ipy_script.py |
| C# script | *script.csx |
| F# script | *script.fsx |
Folders without a supported entry script are skipped.
Use PEP 723 metadata at the top of a Python script:
# /// script
# dependencies = ["polars", "numpy"]
# ///The runtime prepares dependencies before execution. Current behavior is Pixi-first with pip/pyRevit CPython fallback.
Python debugging uses VSCode/debugpy integration when enabled.
The high-level workflow is:
- Start VSCode debugger attach configuration.
- Run the Python script from RevitDevTool.
- Breakpoints should be hit when the debugger connects.
If debugging does not attach, check debugger port configuration, local firewall/security policy, and whether debugpy was installed into the active runtime.
- Run Code Overview
- Modern Python Scripting
- Python Debugging
- Python Ecosystems
- RevitDevTool And pyRevit
- Python Stub Generation
- Run .NET Add-ins
- Scripting Runtimes