MonoGame Framework and Content Pipeline Version Mismatch After Failed Upgrade

Goal: achieve a consistent MonoGame version across the game project’s framework assemblies and the Content Pipeline extension so that runtime loading and content builds succeed after a failed upgrade.

Constraints: a partial upgrade can leave disparate NuGet package versions, conditional references in the project file may lock to different package IDs, and the Pipeline VSIX may not match the framework, which together create uncertainty about which version to standardize and how to keep the project file uniform across team members without introducing content incompatibility.

What steps confirm that all MonoGame NuGet packages resolve to a single version after recovery? How should the Content Pipeline VSIX version be aligned with the framework version when only part of the upgrade succeeded? Should the conditional elements be updated manually or rely on NuGet restore to maintain consistency across developers?