Blog coding and discussion of coding about JavaScript, PHP, CGI, general web building etc.

Saturday, May 14, 2016

MVC 6 - RC1 to RC2 changes

MVC 6 - RC1 to RC2 changes


I have an application that works fine on RC1 of ASP.NET MVC6. I heard that RC2 is going to use CLI instead of DNX command line tools.

Can somebody please tell me:

  1. Will Project.json undergo any change (apart from package versions, of course)? Currently there is entry dnx451 and dnxcore50 under frameworks section. Will they change post RC2?

  2. I know EF7 migrations commands are going to change but are there any code level changes?

  3. Any other major code level change?

I can't use RC2 packages currently since this project is already in development. But trying to get a feel of what all I need to change when RC2 becomes available.

Answer by NikolaiDante for MVC 6 - RC1 to RC2 changes


According to the roadmap, there shouldn't be any major changes:

RC1 - Stabilization

The focus for RC1 will be on polishing existing features, responding to customer feedback and improving performance and reliability. The goal is for RC1 to be a stable and production ready release.

RC2 - Move to .NET CLI

For RC2 we will move ASP.NET 5 to be based on the new cross-platform .NET Core command line toolchain.

Answer by Dan Davies Brackett for MVC 6 - RC1 to RC2 changes


The dev team is maintaining a list of issues for rc2, with labelling for breaking changes. There are lots of them.

Answer by hidden for MVC 6 - RC1 to RC2 changes


In addition to NikilaiDante answer I believe your project.json has mentions of dnx and if you use migrations you have tooling called Ef Commands. Ef commands is being replaced and dnx is deprecated.

In the meantime, you could add support to dnx in rc2 (maybe) using services.AddMvcDnx(); https://github.com/aspnet/Mvc/issues/4187

Answer by VirendraJ for MVC 6 - RC1 to RC2 changes


I believe there would be many code braking changes as ASP.NET 5 is already renamed to ASP.NET Core. So all the nuget packages version name is going to change and one will have to manually work and fix this. As there is no direct migration for now.

Coming back to your question

  • Till RC 1, every ASP.NET Core project is a DNX project but that?s no more valid with RC2 release.
  • In RC2, DNX is gone. It will be replaced via dotnet cli tool.
  • Incremental compilation is back.
  • The ASP.NET team has also moved away from dnx so in project.json dnx would be replaced by net.

Take a look at this - What?s new in ASP.NET Core 1.0 RC2

And earlier this week, .NET team has released a sample RC2 project on github. It was also discussed in last ASP.NET community stand up last week. You can also read A First look at ASP.NET Core 1.0 RC2

Answer by FredyWenger for MVC 6 - RC1 to RC2 changes


According to the newest information, RC2 should be available at mid-May 2016 and final at the end of June 2016: NET Core RC2 ? Improvements, Schedule, and Roadmap


Fatal error: Call to a member function getElementsByTagName() on a non-object in D:\XAMPP INSTALLASTION\xampp\htdocs\endunpratama9i\www-stackoverflow-info-proses.php on line 72

0 comments:

Post a Comment

Popular Posts

Powered by Blogger.