How to do package versions based on TFM condition for CentralPackageVersionManagement?

[japj]

How would one use conditions on the TargetFramework with CentralPackageVersionManagement (using Directory.Packages.props).
In case you have projects with different TargetFramework and needing to use a different version based on the TargetFramework.

Example Directory.Packages.Props

<Project>
  <ItemGroup>
    <PackageVersion Condition=" '$(TargetFramework)' == 'netstandard2.0' " Include="MSTest.TestAdapter" Version="1.1.0" />
    <PackageVersion Condition=" '$(TargetFramework)' == 'net6.0' " Include="MSTest.TestAdapter" Version="3.1.0" />
  </ItemGroup>
</Project>

As far as I can tell the Directory.Packages.Props file is imported before the TargetFramework Property is set in a normal csproj file causing the conditions to evaluate to empty and thus not working.

[erdembayar]

Fyi @jeffkl

[jeffkl]

In MSBuild, all properties and imports are evaluated first. Items are then evaluated second. Since PackageVersion is an item, it is evaluated after all properties even if it is declared before a property. The following works as expected for me:

ClassLibrary1.csproj

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFrameworks>net472;net6.0</TargetFrameworks>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Newtonsoft.Json" />
  </ItemGroup>
</Project>

Directory.Packages.props

<Project>
  <PropertyGroup>
    <!-- Enable central package management -->
    <ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
  </PropertyGroup>
  <ItemGroup>
    <PackageVersion Include="Newtonsoft.Json" Version="12.0.1" Condition="'$(TargetFramework)' == 'net472'" />
    <PackageVersion Include="Newtonsoft.Json" Version="13.0.1" Condition="'$(TargetFramework)' != 'net472'" />
  </ItemGroup>
</Project>

If its not working as expected, please do a command-line based restore and attach msbuild.binlog:

msbuild /Target:Restore /BinaryLogger

[nvmkpk]

Not true, you are multi targeting, in this case it is working because the TFM is set before loading the project for specific TFM. If you specify single TFM using TargetFramework element, it will fail.