LockFile validation fails for projects with <RuntimeIdentifiers> set in SDK 3.0.100

[bergbria]

Details about Problem

NuGet product used: dotnet.exe

dotnet.exe --version: 3.0.100

Worked before?: Yes, with sdk version 2.2.402

Automated Repro

1. Download netSdk3_rid_lockFile_repro.zip
2. Extract
3. Run repro.bat

Manual repro steps

1. Create a .csproj resembling this:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp2.1</TargetFramework>
    <RuntimeIdentifiers>win-x64;osx-x64</RuntimeIdentifiers>
  </PropertyGroup>
</Project>

2. dotnet restore --use-lock-file
   • This will succeed and write a lock file
3. dotnet restore --use-lock-file --locked-mode
   • This will fail with error NU1004: The packages lock file is inconsistent with the project dependencies despite the fact that the file was just generated and nothing has changed.

Tagging @nkolev92 and @rrelyea as FYI.

[anangaur]

@nkolev92, Is this because of the framework libraries now getting folded into the SDK with 3.0?

[bergbria]

@anangaur / @nkolev92 this is related to #7724 / #8442 and possibly has the same root cause. I don't know enough about the implementation to say.

Either way, it's frustrating that this blocks using even newer SDK versions, not just .Net Core 3.

[nkolev92]

I think this is a duplicate of #8645.

The above example will work if the runtime identifiers are sorted.

For example it doesn't repro for me if I do the following:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp2.1</TargetFramework>
    <RuntimeIdentifiers>osx-x64;win-x64</RuntimeIdentifiers>
  </PropertyGroup>
</Project>

Can you please confirm @bergbria

[nkolev92]

I guess the other way around since this issue is older.

[nkolev92]

Fixed by NuGet/NuGet.Client#3075

[bergbria]

@nkolev92 - sorry for not responding. Sorting the RIDs did resolve the issue in my repros, so the fix should resolve it. Thanks!