d365fo-mcp 1.1.0 → 1.2.0

package/README.md

@@ -10,7 +10,7 @@
 [![TypeScript](https://img.shields.io/badge/TypeScript-6.0-blue.svg)](https://www.typescriptlang.org/)
 [![Tests](https://img.shields.io/badge/tests-1400%2B-brightgreen.svg)](docs/TESTING.md)
 <!-- coverage-badge:start -->
-[![Core coverage](https://img.shields.io/badge/core_coverage-79.1%25-yellow.svg)](eval/COVERAGE.md) [![Total coverage](https://img.shields.io/badge/total_coverage-48.1%25-lightgrey.svg)](eval/COVERAGE.md)
+[![Core coverage](https://img.shields.io/badge/core_coverage-100%25-brightgreen.svg)](eval/COVERAGE.md) [![Total coverage](https://img.shields.io/badge/total_coverage-59.7%25-lightgrey.svg)](eval/COVERAGE.md)
 <!-- coverage-badge:end -->
 
 *Grounded AI development for Dynamics 365 Finance & Operations — works with GitHub Copilot and Claude Code*
@@ -74,12 +74,21 @@ Structural violations (wrong order, missing container, disallowed control) **blo
 
 ## Quick Start
 
-**Installing on your own D365FO VM** — the usual case. One line in PowerShell installs the prerequisites, clones the repository and runs the setup wizard, which builds the C# bridge and the metadata index for you:
+**Installing on your own D365FO VM** — the usual case. One line in PowerShell installs Node.js if it is missing, installs the server from npm, and runs the setup wizard, which asks where the index should live and builds the C# bridge for you:
 
 ```powershell
 irm https://raw.githubusercontent.com/dynamics365ninja/d365fo-mcp-server/main/install.ps1 | iex
 ```
 
+Already have Node.js 24+? Then the one-liner has nothing to bootstrap and you can skip it:
+
+```powershell
+npm install -g d365fo-mcp
+d365fo-mcp setup
+```
+
+Re-running either is safe. An installation made before the npm package existed is a git checkout, and both are left exactly where they are and updated in place.
+
 **Your team already runs a shared server?** Then you install nothing — point your editor at it:
 
 ```powershell

package/bridge/D365MetadataBridge/D365MetadataBridge.csproj

@@ -0,0 +1,116 @@
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>net48</TargetFramework>
+    <LangVersion>12.0</LangVersion>
+    <Nullable>enable</Nullable>
+    <RootNamespace>D365MetadataBridge</RootNamespace>
+    <AssemblyName>D365MetadataBridge</AssemblyName>
+    <AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>
+    <!-- Resolve transitive assembly version conflicts in D365FO bin (e.g. SCDP 7.0.0 vs 7.0.4) -->
+    <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
+    <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
+    <!-- MSB3277: version conflict between Microsoft-shipped SCDP.dll (7.0.0) and
+         SCDPBundling.dll (depends on 7.0.4) in PackagesLocalDirectory\bin.
+         We don't control these DLLs and the bridge doesn't use SCDP at all — safe to suppress.
+         MSB3106: some D365FO versions ship MetaModel.Core with a version suffix in the filename
+         (e.g. Microsoft.Dynamics.Framework.Tools.MetaModel.Core.17.0.dll); the wildcard glob
+         picks it up automatically, so the explicit name reference is gone and this warning should
+         no longer appear — kept here as a safety net for edge-case environments. -->
+    <MSBuildWarningsAsMessages>MSB3277;MSB3106</MSBuildWarningsAsMessages>
+  </PropertyGroup>
+
+  <!--
+    D365FO bin directory — contains all Microsoft.Dynamics.*.dll assemblies.
+    Every D365FO development desktop has this directory available.
+
+    Traditional VM:  K:\AosService\PackagesLocalDirectory\bin
+    Cloud-hosted:    C:\AosService\PackagesLocalDirectory\bin
+    UDE (Unified Developer Experience): path from .mcp.json microsoftPackagesPath/bin
+
+    Override per-machine via:
+      dotnet build -p:D365BinPath="C:\path\to\bin"
+    or in a local Directory.Build.props (not committed to source control).
+  -->
+  <PropertyGroup>
+    <D365BinPath Condition="'$(D365BinPath)' == '' And Exists('K:\AosService\PackagesLocalDirectory\bin')">K:\AosService\PackagesLocalDirectory\bin</D365BinPath>
+    <D365BinPath Condition="'$(D365BinPath)' == '' And Exists('C:\AosService\PackagesLocalDirectory\bin')">C:\AosService\PackagesLocalDirectory\bin</D365BinPath>
+  </PropertyGroup>
+
+  <!-- NuGet packages -->
+  <ItemGroup>
+    <PackageReference Include="System.Text.Json" Version="8.0.5" />
+    <PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies.net48" Version="1.0.3">
+      <PrivateAssets>all</PrivateAssets>
+      <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
+    </PackageReference>
+  </ItemGroup>
+
+  <!--
+    D365FO assemblies: auto-referenced from $(D365BinPath) via glob.
+    At runtime, Program.cs dynamically loads them via AppDomain.AssemblyResolve
+    from the - -packages-path argument, so Private=false (don't copy to output).
+  -->
+  <ItemGroup>
+    <Reference Include="Microsoft.CSharp" />
+  </ItemGroup>
+  <ItemGroup Condition="'$(D365BinPath)' != ''">
+    <Reference Include="$(D365BinPath)\Microsoft.Dynamics.*.dll">
+      <Private>false</Private>
+    </Reference>
+  </ItemGroup>
+
+  <!--
+    Record WHICH metamodel build we compiled against, so the bridge can warn at
+    startup when it is pointed at an environment shipping a different one.
+
+    This matters because every platform build stamps the SAME assembly version
+    (7.0.0.0) and differs only in FileVersion (e.g. 7.0.7690.155 vs 7.0.7996.33).
+    The CLR binder therefore cannot tell them apart, and the AssemblyResolve →
+    LoadFrom path in Program.cs does not enforce identity — a mismatched DLL
+    loads silently and only blows up later as MissingMethodException /
+    TypeLoadException at JIT time, far from the cause.  See issue #703.
+  -->
+  <Target Name="CaptureMetamodelBuildVersion"
+          BeforeTargets="BeforeCompile"
+          Inputs="$(D365BinPath)\Microsoft.Dynamics.AX.Metadata.dll"
+          Outputs="$(IntermediateOutputPath)BuildInfo.g.cs">
+    <PropertyGroup>
+      <_MetamodelDll>$(D365BinPath)\Microsoft.Dynamics.AX.Metadata.dll</_MetamodelDll>
+    </PropertyGroup>
+    <GetFileVersion FilePath="$(_MetamodelDll)" Condition="Exists('$(_MetamodelDll)')">
+      <Output TaskParameter="Version" PropertyName="_MetamodelFileVersion" />
+    </GetFileVersion>
+    <Message Importance="high"
+             Text="Bridge compiles against metamodel $(_MetamodelFileVersion) from $(D365BinPath)"
+             Condition="'$(_MetamodelFileVersion)' != ''" />
+    <Warning Text="D365BinPath '$(D365BinPath)' has no Microsoft.Dynamics.AX.Metadata.dll — the runtime version check will be disabled."
+             Condition="'$(_MetamodelFileVersion)' == ''" />
+    <WriteLinesToFile File="$(IntermediateOutputPath)BuildInfo.g.cs" Overwrite="true" WriteOnlyWhenDifferent="true"
+                      Lines="// &lt;auto-generated /&gt; Produced by the CaptureMetamodelBuildVersion target.;namespace D365MetadataBridge;{;    internal static class BuildInfo;    {;        /// &lt;summary&gt;FileVersion of the Microsoft.Dynamics.AX.Metadata.dll this build compiled against, or &quot;&quot; if unknown.&lt;/summary&gt;;        internal const string MetamodelFileVersion = &quot;$(_MetamodelFileVersion)&quot;%3B;        /// &lt;summary&gt;bin directory those reference assemblies came from, or &quot;&quot; if unknown.&lt;/summary&gt;;        internal const string MetamodelBinPath = @&quot;$(D365BinPath)&quot;%3B;    };}" />
+    <ItemGroup>
+      <Compile Include="$(IntermediateOutputPath)BuildInfo.g.cs" />
+      <FileWrites Include="$(IntermediateOutputPath)BuildInfo.g.cs" />
+    </ItemGroup>
+  </Target>
+
+  <!--
+    MSBuild has no built-in task for reading a file's FileVersion (GetAssemblyIdentity
+    returns the assembly version — 7.0.0.0 for every platform build, which is exactly
+    the value that cannot distinguish them).
+  -->
+  <UsingTask TaskName="GetFileVersion" TaskFactory="RoslynCodeTaskFactory"
+             AssemblyFile="$(MSBuildToolsPath)\Microsoft.Build.Tasks.Core.dll">
+    <ParameterGroup>
+      <FilePath ParameterType="System.String" Required="true" />
+      <Version ParameterType="System.String" Output="true" />
+    </ParameterGroup>
+    <Task>
+      <Code Type="Fragment" Language="cs">
+        Version = System.Diagnostics.FileVersionInfo.GetVersionInfo(FilePath).FileVersion ?? "";
+      </Code>
+    </Task>
+  </UsingTask>
+
+</Project>