What problems do you see with asp.net core to state that it is not production ready ? There are still hiccups with Entity Framework 7 and unless you work in a very adventurous team, most teams and projects out there are based on ASP.NET MVC 5 or earlier. Having said all that, in my opinion, ASP.NET Core 1 is not quite production yet. I’m planning to create a short (1 – 2 hour) course that helps developers with knowledge of ASP.NET MVC 5 transition to the new ASP.NET. None of these are revolutionary! You can get up to speed with them by reading a few tutorials or watching a few videos. There are some improvements in the framework and the tooling. More than 90% of what you learn is the same in the new ASP.NET. If you have little or no experience with ASP.NET MVC (any versions), and you’d like to learn it from me, your best source is my Complete ASP.NET MVC 5 course.ĪSP.NET Core 1 is based on the same principles you learn in that course. Scott Hanselman has explained the rationale behind these name changes perfectly in his post. You’re not the only one frustrated about these name changes! It started as ASP.NET vNext, then changed to ASP.NET 5, next was renamed to ASP.NET MVC 6 and eventually became ASP.NET Core 1.0. Yes, the version number is confusing! It has gone through a few name changes. ASP.NET xĪSP.NET Core 1 is the next version of ASP.NET MVC 5. So I thought to turn this into a short blog post. What is the difference between ASP.NET MVC 5, ASP.NET MVC 6, ASP.NET 5 and ASP.NET Core 1? Should I learn ASP.NET MVC 5 or ASP.NET Core 1?

August 13th, 2016 Comments Should you learn ASP.NET MVC 5 or ASP.NET Core 1?Ī common question that I get a lot lately:

Asp net mvc tutorials