Doing a dotnet restore for a project targeting just netstandard2.0 or the like, and not more specialized than that, will not produce runtime assembly versions to be used in the dependency graph generation.
We're not able to get dotnet to give us a more precise information about the specific runtime versions being used, and I suspect it is because of what you see in this matrix.
Basically that .NET cannot get more specific because netstandard really encompasses the large amount of different frameworks.
This PR
Stops the flow from trying to find runtimepack.* information in the .deps files
Adds tests related to this
Also did some small housekeeping of tests (wrongly named folders and such)
Doing a
dotnet restore
for a project targeting justnetstandard2.0
or the like, and not more specialized than that, will not produce runtime assembly versions to be used in the dependency graph generation.We're not able to get
dotnet
to give us a more precise information about the specific runtime versions being used, and I suspect it is because of what you see in this matrix.Basically that .NET cannot get more specific because
netstandard
really encompasses the large amount of different frameworks.This PR
runtimepack.*
information in the.deps
files