Skip to content

host-boundaries.md

Latest commit

 

History

History
46 lines (35 loc) · 2.49 KB

host-boundaries.md

File metadata and controls

46 lines (35 loc) · 2.49 KB
Raw

Host Boundaries

The platform is host-agnostic by design. Every feature should be sharable across hosts by default. Only features that inherently require a specific host API (e.g. Revit DirectContext3D geometry) belong in host projects. Revit and AutoCAD are current hosts; future hosts can be added through adapters.

Shared Layer

Keep these host-neutral — this is the default for all new functionality:

  • source/DevTools.Execution/
  • source/DevTools.Logging/
  • source/DevTools.McpParser/
  • source/DevTools.McpServer/
  • source/DevTools.Presentation/
  • source/DevTools.Settings/
  • source/DevTools.Telemetry/
  • source/DevTools.UI/
  • source/DevTools.Utilities/

Host Layer

Host API references belong in host projects:

  • Revit host: source/RevitDevTool/
  • Revit-only core: source/RevitDevTool.Core/ (RevitContext, RevitTransactionService, dockable pane loader, image exporter — not shared with other hosts)
  • AutoCAD host: source/AcadDevTool/
  • Visualization: source/RevitDevTool/Visualization/ (DirectContext3D — entirely Revit-host, not in shared code)
  • Future hosts: add new host projects rather than extending shared code with platform-specific branches.

Standalone Process

  • source/DevTools.McpServer/ runs outside hosts as MCPServer.exe.
  • InstanceManager discovers any host pipe via generic regex ({HostApp}_{Version}_{PID}).
  • HostBridgeClient connects to any host (formerly RevitBridgeClient).
  • Standalone built-in tools: list_host_instances, launch_host, read_file_info, open_model (multi-host).
  • In-host built-in tools (shared runtime): execute_csharp_code, open_document via IDocumentBridge.
  • Startup dialog resolver uses merged keywords in default StartupDialogResolverOptions (Revit + AutoCAD).
  • Remaining gaps for AutoCAD: no shipped MCP toolset.

Boundary Checklist

  • Default: new features go into shared DevTools.* libraries unless they require host-specific APIs.
  • Shared services should depend on interfaces, not Revit/AutoCAD/Tekla/Bentley APIs.
  • Host projects should implement adapters for command discovery, host context execution, script bridges, debugger bridges, document bridge (IDocumentBridge), and visualization.
  • UI/view models in shared presentation code should expose host-neutral behavior.
  • Host-specific rendering, transactions, threading, and document context must stay in host projects.
  • When adding a feature to one host, evaluate whether the design can be shared or extracted into a shared abstraction for future hosts.