Open-source Revit MCP server: let Claude and other AI assistants read and edit BIM models, with human approval on every change.
Python aecai-agentsautodeskautomationbimclaudeifcmcpmcp-servermodel-context-protocolnavisworksrevitrevit-addinrevit-apirhino
Add target frameworks and dependencies guide (#11)
A. Sam Mohammadbb7ee42feb0f
diff --git a/docs/target-frameworks-and-dependencies.md b/docs/target-frameworks-and-dependencies.mdnew file mode 100644index 0000000..2b90d69--- /dev/null+++ b/docs/target-frameworks-and-dependencies.md@@ -0,0 +1,68 @@+# Target Frameworks And Dependencies++This repository is intentionally polyglot. The Python MCP server and the Revit add-in do not share the same runtime constraints.++## Python Package++The Python package metadata lives in [packages/mcp-server-revit/pyproject.toml](../packages/mcp-server-revit/pyproject.toml).++Current characteristics:++- package name: `revit-mcp-server`+- Python requirement: `>=3.11`+- validation and settings stack: `pydantic`, `pydantic-settings`+- transport stack: `httpx`+- environment loading: `python-dotenv`+- development and test dependencies are defined inline rather than split into a separate requirements file++## Revit Add-in Targets++The add-in project file is [packages/revit-bridge-addin/RevitBridge.csproj](../packages/revit-bridge-addin/RevitBridge.csproj).++It conditionally targets:++- `net48` for Revit 2024 and earlier project settings+- `net8.0-windows` when `RevitVersion == 2025`++That dual-target behavior is one of the most important build facts in the repo.++## Revit API Reference Strategy++The add-in first tries to bind against locally installed Revit assemblies:++- `RevitAPI.dll`+- `RevitAPIUI.dll`++If those are not present, it falls back to NuGet packages:++- `Nice3point.Revit.Api.RevitAPI`+- `Nice3point.Revit.Api.RevitAPIUI`++This makes CI and local developer environments more forgiving, while still supporting direct machine installs with real Autodesk binaries.++## Additional Add-in Dependencies++The C# layer also references:++- `Serilog`+- `Serilog.Sinks.File`+- `System.Text.Json`+- `IronPython` 2.7 on `net48`+- `IronPython` 3.4.1 on `net8.0-windows`++The conditional IronPython dependency exists because the repo exposes an `execute_python` bridge command.++## Temporary Compile Exclusions++`RevitBridge.csproj` currently removes several command directories from compilation:++- `src\Commands\Core\**\*.cs`+- `src\Commands\Advanced\**\*.cs`+- `src\Commands\Specialized\**\*.cs`+- `src\Commands\Enhancements\**\*.cs`++That means the source tree advertises a broader command surface than the compiled binary necessarily includes at the moment.++## Operational Rule++When a build succeeds locally but not in CI, check target framework and dependency resolution before debugging the business logic. In this repo, version-conditional framework selection is part of normal operation, not an edge case.