如何修复旧.NET解决方案添加NuGet包时的$(NETStandardImplicitPackageVersion)错误

I've run into this exact issue before when adding a new ASP.NET Core project to an existing legacy .NET solution. The root cause is almost always that one of your older projects (likely a .NET Framework project) is incorrectly referencing the $(NETStandardImplicitPackageVersion) variable in its package references—this variable is only intended for .NET Core/.NET Standard projects, so legacy projects can't resolve it, causing the version parsing error you see.

Here are the step-by-step fixes you can try without rebuilding the entire solution:

• Audit all .csproj files for invalid version references
  Open every project's .csproj file in your solution (you can right-click a project in Visual Studio and select "Edit Project File") and search for any line that uses $(NETStandardImplicitPackageVersion) in a <PackageReference> element. It might look like this:

  <PackageReference Include="Microsoft.Extensions.Logging" Version="$(NETStandardImplicitPackageVersion)" />
  

  Replace this variable with a concrete version number (e.g., 6.0.0 if that's compatible with your project) or a variable that your legacy project can resolve (like $(TargetFrameworkVersion) adjusted to match package versions).

• Clean up NuGet caches and build artifacts
  Sometimes cached files can cause lingering issues. Do the following:

  1. Close Visual Studio completely
  2. Delete the bin and obj folders from every project in your solution
  3. Open a command prompt and run:

     dotnet nuget locals all --clear
     

  4. Reopen your solution and try restoring/installing NuGet packages again

• Check solution-level NuGet.Config
  Look for a NuGet.Config file at the root of your solution. If it exists, check for any global version settings that might be using $(NETStandardImplicitPackageVersion) (for example, in <dependencyVersion> or <packageVersion> sections). Correct any invalid references here to use valid version strings or appropriate variables.

• Switch legacy projects back to packages.config (if applicable)
  If your older .NET Framework projects were recently migrated to PackageReference and started having this issue, you can revert them to using packages.config:

  1. Right-click the legacy project in Visual Studio
  2. Select "Manage NuGet Packages"
  3. Click the gear icon in the top-right corner of the NuGet Package Manager
  4. Under "Package Management", change the default format back to packages.config for that project
  5. Restore packages again

After applying these fixes, try installing a test package (like Newtonsoft.Json) to verify the error is resolved.

内容的提问来源于stack exchange，提问作者Buddy J