Fixed

• AutoCAD and Civil 3D list the commands of a DLL that has WPF views. Before, such a DLL showed no commands.
• A type or method whose references cannot be resolved no longer hides the other commands of the DLL. It is skipped,
  and the host log names it.
• An AutoCAD command declared with a group, such as [CommandMethod("GROUP", "NAME", CommandFlags.Modal)], shows its
  command name instead of the group name.

Added

• Python 3.14 support; development and CI run on 3.14, the Python inside the host.

Changed

• Moved into the RevitDevTool repository; no behavior change.

Changed

• The TestRunner ships inside the package under tools/runner. The adapter no longer looks for a runner in the RevitDevTool install folder.
• The NUnit, TUnit, and MSTest runtimes come from the RevitDevTool add-in. The package keeps only the test host side.
• The framework versions the runtimes were built against are NUnit 5.0.0, TUnit 1.81.10, and MSTest 4.5.2. A newer version with the same major works.

Requirements

• The RevitDevTool 4.0.0-beta.8 add-in or later. An older add-in stops the run with a sentence that says to update it.
• The .NET 10 runtime or later on the machine that runs dotnet test.

The signed channels.json the Daemon reads.

Changed

• Updates come from a signed channels.json. The Daemon and the add-in update separately, each from the channel the
  install is on (stable or prerelease).
• Daemon updates download a delta when the feed holds the installed version, otherwise the full package.
• The add-in update installs one zip per host and host version, so a busy Revit no longer holds back the AutoCAD
  update. installation.json moves to %APPDATA%\RevitDevTool.
• Developer diagnostics are no longer logged in the release build.

Removed

• The GitHub release lookup. The updater reads only the signed channel.

Upgrade

• RevitDevTool 4.0.0-beta.7 and earlier cannot read the new channel. Install this version once with
  RevitDevTool-Setup.exe; later versions arrive through the Updates tab.

Changed

• One bundle per host: RevitDevTool.bundle and AcadDevTool.bundle. A Revit-only install no longer carries AutoCAD
  files.
• The add-in updates on its own channel, one zip per host and host version, so a busy Revit no longer holds back the
  AutoCAD update. installation.json moves to %APPDATA%\RevitDevTool.
• NUnit, TUnit, and MSTest run from the test project's output. The add-in no longer ships a test framework, so a
  newer framework of the same major needs no add-in update. Use RevitDevTool.TestAdapter 0.3.0 or later.
• A test run that cannot start (framework too old, framework missing, add-in too old) stops with one sentence that
  names the fix.
• Telerik, Syncfusion, and DevExpress assemblies are shared with the host instead of loaded twice.
• Developer diagnostics are no longer logged in the release build.

Fixed

• NUnit no longer hangs the host when another add-in leaves its own synchronization context on the main thread.
• NUnit async tests run without another add-in supplying their dependencies, and show their source location.
• An empty test selection runs nothing instead of the whole assembly.
• On .NET Framework hosts (Revit 2024 and earlier), another
  runner's tests no longer get a session's NUnit and run zero tests.

Upgrade

• Needs RevitDevTool (Daemon) 4.0.0-beta.8 or later. Install it with RevitDevTool-Setup.exe; 4.0.0-beta.7 and
  earlier cannot read the new channel.

Full Changelog: 4.0.0-beta.6...4.0.0-beta.7

Full Changelog: 4.0.0-beta.5...4.0.0-beta.6

Compatibility

This release changes how the parts of RevitDevTool check that they can work together (ADR 0055). Update everything together:

• RevitDevTool.TestAdapter 0.2.0 and revitdevtool_pytest 0.6.0 need this release or later. Older adapters and pytest plugins stop with a message that names the update.
• A new adapter against RevitDevTool 4.0.0-beta.4 or older shows Testing protocol version 0 is not supported. Update RevitDevTool.
• After updating, restart Revit or AutoCAD before running tests, so the host loads the new add-in.
• The MCP gateway now rejects Daemons from before this release. Update the Daemon to reconnect the tunnel.
• Test projects need MSTest 4.5.2 and TUnit 1.78.0. A test project on the old pins fails at generation.

Added

• The Daemon window, the Revit dock pane and floating window, and the AutoCAD palette show the product version (DevTools 4.0.0-beta.5).
• Version checks by protocol range for the test adapter, TestRunner, add-in, pytest, and the MCP gateway. A mismatch ends with one sentence that names both sides and the update to make.
• When the gateway rejects the Daemon, the Daemon stops reconnecting and shows "Not compatible with the gateway".

Changed

• A Daemon update to a higher major waits while an add-in of that major is waiting for its host to close. Minor updates do not wait.
• Microsoft.Testing.Platform 2.5.2, MSTest 4.5.2, TUnit 1.78.0.
• Sentry releases use the full product version, including the prerelease suffix.

Fixed

• When pytest stops before running tests (for example a missing node id), the result names the exit code and the node ids instead of "No result received from host for this test."

Full Changelog: 4.0.0-beta.4...4.0.0-beta.5

Full Changelog: 4.0.0-beta.3...4.0.0-beta.4