Resolve nuget package graph for .NET projects together by JohnMcPMS · Pull Request #5627 · microsoft/winget-cli
Issue
When trying to create the actual package containing the MCP server, we found issues in merging the directory contents. Specifically, some common nuget packages were used at different versions.
Change
Reference the MCP project from the configuration server project, forcing the nuget package resolution to consider them as one unit. This also helpfully outputs them as merged already.
Also change the name of the directory in the package to reflect the expanded contents.
Validation
My locally built package works for both MCP and configuration scenarios.