winget install --id=Sharafutdinov.RevitDevLoader -e Versioned test plugins for Revit, installed from a feed and loaded from separate run folders.
For Revit add-in developers who test builds across Revit 2022-2026: install versioned test plugins from a feed, run each version from its own folder, and update or uninstall without touching files that Revit has already loaded.
revit-devloader--user-setup.exe from the latest release. Use revit-devloader--admin-setup.exe to install for all users on the machine.The release also carries revit-devloader-.zip with install.ps1 for scripted installs and SHA256SUMS.txt for every asset; see the installer guide. After the WinGet listing is accepted, winget install Sharafutdinov.RevitDevLoader installs the same user setup.
Verify downloads with GitHub CLI to check the build provenance before installing.
First feed. Open Settings in the manager and enter a feed repository, release tag and feed.json asset name. The demo feed is repository sharafutdinovdi/revit-devloader, tag demo-feed, asset feed.json; it lists three sample plugins for Revit 2025 and 2026. GitHub release feeds need GitHub CLI in PATH and gh auth login on that Windows account. There is no default feed.
Recorded in Revit 2026 against the demo feed. The catalog lists the three packages from samples/ with their icons. Install adds the Hello Plugin button and the plugin runs. A newer version reaches the feed, Check for updates shows 1.0.0 → 1.1.0 and Update installs it. Uninstall removes the registration and hides the button.
plugin.json manifest, per-year assemblies and PNG icons; older key-value packages still load.| Component | Responsibility |
|---|---|
| Feed | JSON registry with releases, package URLs, sizes and SHA-256 hashes |
| Package cache | Downloads through gh or HTTPS, verifies size and hash before extraction |
| Run folder | One directory per installation under %LOCALAPPDATA%\RevitDevLoader\plugins |
| Registry | .devmanifest files that map installed packages to run folders and commands |
| Ribbon | Buttons resolve the installed assembly and invoke the command through reflection |
Details: how it works, feed format and publishing, plugin package format, roadmap and known gaps.
| Add-in | Revit years | Target framework |
|---|---|---|
| Legacy | 2022, 2023, 2024 | net48 |
| Modern | 2025, 2026 | net8.0-windows |
Windows only. Revit API references restore from NuGet per year; no Autodesk assemblies ship in any artifact. Command loading does not unload previously loaded assemblies, and replacing an application plugin requires a Revit restart.
Read CONTRIBUTING.md for the build from source, the sample plugin walkthrough and the release ritual. Bugs and feature requests use the issue forms; questions go to Discussions; vulnerabilities follow SECURITY.md.
170 xUnit tests cover feed parsing, package extraction, registry writes, run retention, settings and manager state, and run on every push without Revit. Windows CI then builds all five Revit years, checks the release layout, and installs and removes both setup executables. See the changelog for what changed in each version.
MIT. Author and maintainer: Dinar Sharafutdinov. Third-party licenses are listed in THIRD-PARTY-NOTICES.md.