ASP.NET 5 beta5 update breaks everything

Question

I followed this guide when upgrading to beta5, and the upgrade process seems to have worked.

http://blogs.msdn.com/b/webdev/archive/2015/06/30/asp-net-5-beta5-now-available.aspx

To upgrade ASP.NET 5 Beta5, follow these steps:

• Install .NET Version Manager (DNVM) if you don’t already have one (it comes preloaded with Visual Studio 2015 RC, or you can get the latest version)
• At the command line, set the DNX_FEED environment variable https://www.nuget.org/api/v2
• Run the "dnvm upgrade". In your application, update the global.json file to point to the beta version of the .NET runtime environment (DNX) beta
• Also your project.json will point to beta5 package versions
• Run "dnu restore" Run "dnu build" and transfer your code to the required beta5.

However, I get assembly errors that say I don't have assemblies. He complains about System.Void and this is not enough. He also cannot find the controller from Microsoft.AspNet.MVC: /

If I go back to beta 4, it will work again.

What step am I missing?

DNVM List ( Reverts to Beta 4)

Active Version Runtime Architecture Location Ali as ------ ------- ------- ------------ -------- --- 1.0.0-beta4 clr x64 C:\Users\MySelf\.dnx\runtimes * 1.0.0-beta4 clr x86 C:\Users\MySelf\.dnx\runtimes 1.0.0-beta4 coreclr x64 C:\Users\MySelf\.dnx\runtimes 1.0.0-beta4 coreclr x86 C:\Users\MySelf\.dnx\runtimes 1.0.0-beta5 clr x86 C:\Users\Myself\.dnx\runtimes def 1.0.0-beta5-12103 clr x86 C:\Users\MySelf\.dnx\runtimes 

Answer 1

I just updated the Visual Studio 2015 ASP.MVC web application from beta to beta 5 and am now launching it. Below are some additions to the instructions that you have followed.

Run "dnvm upgrade"

After that, this is what dnvm list will output.

 Active Version Runtime Architecture Location Alias ------ ------- ------- ------------ -------- ----- 1.0.0-beta4 clr x64 C:\Users\BigFont\.dnx\runtimes 1.0.0-beta4 clr x86 C:\Users\BigFont\.dnx\runtimes 1.0.0-beta4 coreclr x64 C:\Users\BigFont\.dnx\runtimes 1.0.0-beta4 coreclr x86 C:\Users\BigFont\.dnx\runtimes * 1.0.0-beta5 clr x86 C:\Users\BigFont\.dnx\runtimes default 1.0.0-beta5-12087 clr x86 C:\Users\BigFont\.dnx\runtimes 

In your application, update your global.json to point to beta5

In global.json specify the specific beta5 build:

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

Also your project.json points to beta5 package versions

In project.json beta5 link. This will force dnu to restore the latest build ( well, curious - David Fole describes the nuances of the "floating version" here. )

 "dependencies": { "Microsoft.AspNet.Server.IIS": "1.0.0-beta5", "Microsoft.AspNet.Server.WebListener": "1.0.0-beta5", "Microsoft.AspNet.StaticFiles": "1.0.0-beta5" }, 

... port your code to beta5 as needed

Once you stop accepting errors about missing base objects, such as System.Void , you can get errors about changes being made. This may require some research to resolve, depending on what your code base is using. For example, if you use the ASP.NET identifier, you need to change this:

 SignInManager.PasswordSignInAsync( model.Email, model.Password, model.RememberMe, shouldLockout: false); 

:

 SignInManager.PasswordSignInAsync( model.Email, model.Password, model.RememberMe, lockoutOnFailure: false); 

Final Note: Visual Studio

Closing and reopening the solution in Visual Studio can solve recovery / build problems after updating the global.json and package.json files.

See also: ASP.NET 5 Web Project (vNext): Updating Conflict Conflict from Beta to Beta

Answer 2

@Shaun Luttin covers it, but I mentioned two things:

• The browser link doesn’t actually work in beta 5. This causes a very strange error. You need to comment on app.UseBrowserlink() to make everything work. Later versions have fixed this problem.
• I also found that packages with "ConfigurationModel" in the name were renamed to "Configuration".