nuget build is jacked

[johns10]

Thanks for making this library. It's solved my use case for dynamically building MCP servers ... and it's modern and nice to use.

I think the nuget publishing is busted. If I run this and pull from nuget, I get:

Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'ModelContextProtocol.NET.Core, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.

File name: 'ModelContextProtocol.NET.Core, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'
   at MCP.ServerAdapter.Program.Main(String[] args)
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
   at MCP.ServerAdapter.Program.Main(String[] args)
   at MCP.ServerAdapter.Program.<Main>(String[] args)

But if I reference it locally, it runs fine.

I made a minimal repo (basically copied calculator) and it exhibits the issue:

https://github.com/johns10/ModelContextProtocol.NetBuildIssue

I don't know much about building in .net land, but Cline thinks you need to add explicit versions to the .csproj files like this:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <Description>
      Core models, interfaces, and utilities for the Model Context
      Protocol (MCP)
    </Description>
    <Version>0.3.2-alpha</Version>
    <AssemblyVersion>0.3.2.0</AssemblyVersion>
    <FileVersion>0.3.2.0</FileVersion>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="FluentValidation" />
  </ItemGroup>
</Project>

[salty-flower]

Hi, thanks for pointing out! As it's also my first time publishing a NuGet package, I am not sure either what exactly is the cause. I'll have a look at it soon!