dnx 1.0.0-beta7-12331, dnu restore issue

[causer]

After installing the nightly build I am trying to do a dnu restore. I get the following errors:

Errors in C:\Users\vyacheslav\Documents\Visual Studio 2015\Projects\WebApplicati
on8\src\WebApplication8\project.json
    Unable to locate Microsoft.Win32.Registry >= 4.0.0-beta-23210
    Unable to locate System.Diagnostics.Process >= 4.0.0-beta-23210
    Unable to locate System.Net.NetworkInformation >= 4.0.10-beta-23210
    Unable to locate System.Security.Principal.Windows >= 4.0.0-beta-23210
    Unable to locate System.Threading.ThreadPool >= 4.0.10-beta-23210
    Unable to locate System.Reflection.Extensions >= 4.0.1-beta-23210
    Unable to locate System.Text.Encoding.Extensions >= 4.0.11-beta-23210
    Unable to locate System.Threading >= 4.0.11-beta-23210
    Unable to locate System.Collections >= 4.0.11-beta-23210
    Unable to locate System.Threading.Tasks >= 4.0.11-beta-23210
    Unable to locate System.IO >= 4.0.11-beta-23210
    Unable to locate System.Console >= 4.0.0-beta-23210
    Unable to locate System.Collections.Concurrent >= 4.0.11-beta-23210
    Unable to locate System.Text.RegularExpressions >= 4.0.11-beta-23210
    Unable to locate System.IO.FileSystem.Primitives >= 4.0.1-beta-23210
    Unable to locate System.IO.FileSystem >= 4.0.1-beta-23210
    Unable to locate System.IO.FileSystem.Watcher >= 4.0.0-beta-23210
    Unable to locate System.Runtime.Extensions >= 4.0.11-beta-23210
    Unable to locate System.Text.Encoding >= 4.0.11-beta-23210
    Unable to locate System.Security.Claims >= 4.0.1-beta-23210
    Unable to locate Microsoft.Win32.Primitives >= 4.0.1-beta-23210
    Unable to locate System.Security.Cryptography.X509Certificates >= 4.0.0-beta
-23210
    Unable to locate System.Threading.Overlapped >= 4.0.1-beta-23210
    Unable to locate System.Diagnostics.Contracts >= 4.0.1-beta-23210
    Unable to locate System.Net.WebSockets >= 4.0.0-beta-23210
    Unable to locate System.Security.Cryptography.Hashing.Algorithms >= 4.0.0-be
ta-23210
    Unable to locate System.Threading.Timer >= 4.0.1-beta-23210
    Unable to locate System.Resources.ResourceManager >= 4.0.1-beta-23210
    Unable to locate System.Linq >= 4.0.1-beta-23210
    Unable to locate System.Diagnostics.Tools >= 4.0.1-beta-23210
    Unable to locate System.Net.Primitives >= 4.0.11-beta-23210
    Unable to locate System.Diagnostics.Debug >= 4.0.11-beta-23210
    Unable to locate System.ComponentModel.Annotations >= 4.0.11-beta-23210
    Unable to locate System.ComponentModel.TypeConverter >= 4.0.1-beta-23210
    Unable to locate Microsoft.CSharp >= 4.0.1-beta-23210
    Unable to locate System.Runtime >= 4.0.21-beta-23210
    Unable to locate System.Globalization >= 4.0.11-beta-23210

NuGet Config files used:
    C:\Users\vyacheslav\AppData\Roaming\NuGet\NuGet.Config
    C:\Users\vyacheslav\Documents\Visual Studio 2015\Projects\WebApplication8\Nu
Get.Config

Feeds used:
    https://www.myget.org/F/aspnetvnext/api/v2/
    https://www.myget.org/F/roslyn-nightly/
    https://www.myget.org/F/dotnet-corefx/

My project.json file:

{
  "webroot": "wwwroot",
  "version": "1.0.0-*",

  "dependencies": {
    "Microsoft.AspNet.Server.IIS": "1.0.0-beta7-*",
    "Microsoft.AspNet.Server.WebListener": "1.0.0-beta7-*",
    "Microsoft.AspNet.Mvc.ViewFeatures": "6.0.0-beta7-*"
  },

  "commands": {
    "web": "Microsoft.AspNet.Hosting --config hosting.ini"
  },

  "frameworks": {
    "dnx451": { },
    "dnxcore50": { }
  },

  "publishExclude": [
    "node_modules",
    "bower_components",
    "**.xproj",
    "**.user",
    "**.vspscc"
  ],
  "exclude": [
    "wwwroot",
    "node_modules",
    "bower_components"
  ]
}

My global.json file:

{
    "projects": [ "src", "test" ],
    "sdk": {
        "version": "1.0.0-beta7-12331"
    }
}

Any thoughts?

[kevinchalet]

These weird issues are caused by the fact various ASP.NET 5 packages reference CoreCLR packages that are not on MyGet/NuGet yet (23210 > 23207).

@davidfowl curious: shouldn't DNU automatically use the latest available version when it cannot find the specific build referenced in a package?

[davidfowl]

Not if the dependency constraint is violated. If you depend on >= 4.0.20 and only 4.0.10 is there, it will fail.

[kevinchalet]

Well, it's a bit more subtle: when we specify 4.0.1-beta-* in project.json, it's automatically converted to 4.0.1-beta-[build available when the package is created] in .nuspec (for instance, 4.0.1-beta-23210).

But since we used a wildcard in project.json (4.0.1-beta-*) to indicate we wanted to reference the latest build, 4.0.1-beta-23207 (the latest version found) should be considered as a valid version.

[davidfowl]

But since we used a wildcard in project.json (4.0.1-beta-*) to indicate we wanted to reference the latest build, 4.0.1-beta-23207 (the latest version found) should be considered as a valid version.

That does work but the above project.json would need to specify all of the transitive dependencies as * which kinda defeats the purpose.

[kevinchalet]

@causer FYI, the missing packages are now on MyGet! 😄

[causer]

@PinpointTownes Thank you, now 'dnu restore' reports "Done, without errors, Restore complete". I should close this issue?