Microsoft.NETCore.App cannot be restored on projects with netstandard1.0, netstandard1.1, netstandard1.2, netstandard1.3, netstandard1.4.

Expectations

Microsoft.NETCore.App currently targets netstandard1.0 which lead me to believe it’d be possible (although not recommended) to use it in a >= netstandard1.0 project. However, it seems that the package is hand crafted and has dependencies that are inconsistent with its actual TFM.

Steps to reproduce

• Create a project with the project.json:

{
  "dependencies": {
    "Microsoft.NETCore.App": {
      "type": "platform",
      "version": "1.0.0-*"
    }
  },
  "frameworks": {
    "netstandard1.0": {
      "dependencies": {}
    }
  }
}

You can can change the netstandard1.0 tfm to 1.1, 1.2, 1.3 or 1.4 and get the same behavior

• Run dotnet restore

Expected behavior

• Restore completes successfully because Microsoft.NETCore.App’s nupkg says it targets netstandard1.0.

Actual behavior

• Restore fails because Microsoft.NETCore.App actually targets packages that depend on netstandard1.5

Attached error log: restoreerror.txt

Environment data

.NET Command Line Tools (1.0.0-rc2-002678)

Product Information: Version: 1.0.0-rc2-002678 Commit Sha: 3b2ea9d14b

Runtime Environment: OS Name: Windows OS Version: 10.0.10586 OS Platform: Windows RID: win10-x64

This seems like a blocker since the Microsoft.NETCore.App is the bread and butter to .NET core but I’ll let the higher powers decide.

/cc @Eilon @DamianEdwards @davidfowl

[brthor]

@NTaylorMullen deleted the comment right after I posted it, since I realized this issue was not about quite the same thing. 😄

[guardrex]

@joganet That’s correct. You do have the TFM’s correct. My packages are netstandard1.5, and my apps are netcoreapp1.0. Yeah … unfreeze and perhaps check for lingering old SDK’s and dotnet cli’s in Programs & Features.

Worst case scenario is that you’ll have to put up a repro so that a MS dev can pull it down and see what’s what with the problem. They’re monitoring our conversation 👀, and when they don’t jump in quickly, it usually means that they are waiting to see if the ordinary troubleshooting advice works or fails. The next step will be ‘please give us a GH repro … a lib and an app that we can test.’