How can I pin FluentAssertions to version 7.1.0 using Central Package Management in .NET SDK projects?

Below is an explanation of how to pin a NuGet package version when using Central Package Management.

How It Works

When you enable Central Package Management by setting:

XMLCopied
<ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>

in your Directory.Build.props, you delegate version management to the centrally defined file. By declaring a package version in your Directory.Packages.props file, every project referencing that package without specifying an inline version will use the centrally specified version.

Pinning FluentAssertions to Version 7.1.0

In your Directory.Packages.props you already have:

XMLCopied
<Project>
  <ItemGroup Condition="$(IsTestProject) == 'true'">
    <PackageVersion Include="FluentAssertions" Version="7.1.0" />
  </ItemGroup>
</Project>

This ensures that all test projects (based on the condition) that reference FluentAssertions will use version 7.1.0. In your test project’s csproj you only need a simple PackageReference:

XMLCopied
<Project Sdk="Microsoft.NET.Sdk">
  <PackageReference Include="FluentAssertions" />
</Project>

NuGet Package Manager Notifications

Because the package version is centrally managed and pinned to 7.1.0, NuGet Package Manager should not notify you about newer versions—even if a new release appears. This is because the update of a centrally pinned package version requires an explicit change to Directory.Packages.props.

Summary

Yes, you can pin FluentAssertions to 7.1.0. Simply add the following to your Directory.Packages.props:

XMLCopied
<Project>
  <ItemGroup Condition="$(IsTestProject) == 'true'">
    <PackageVersion Include="FluentAssertions" Version="7.1.0" />
  </ItemGroup>
</Project>

And in your test projects’ csproj, ensure you only use the PackageReference without an inline version. This setup ensures that your tests will always use FluentAssertions 7.1.0 without unwanted upgrades notified by NuGet.