Scott Hanselman

ASP.NET 5 is dead - Introducing ASP.NET Core 1.0 and .NET Core 1.0

1月 19, '16 コメント [17] Posted in ASP.NET | Open Source
Sponsored By

Naming is hard.

There are only two hard things in Computer Science: cache invalidation and naming things. - Phil Karlton

It's very easy to armchair quarterback and say that "they should have named it Foo and it would be easy" but very often there's many players involved in naming things. ASP.NET is a good 'brand' that's been around for 15 years or so. ASP.NET 4.6 is a supported and released product that you can get and use now from http://get.asp.net.

However, naming the new, completely written from scratch ASP.NET framework "ASP.NET 5" was a bad idea for a one major reason: 5 > 4.6 makes it seem like ASP.NET 5 is bigger, better, and replaces ASP.NET 4.6. Not so.

So we're changing the name and picking a better version number.

Reintroducing ASP.NET Core 1.0 and .NET Core 1.0

  • ASP.NET 5 is now ASP.NET Core 1.0.
  • .NET Core 5 is now .NET Core 1.0.
  • Entity Framework 7 is now Entity Framework Core 1.0 or EF Core 1.0 colloquially.

Why 1.0? Because these are new. The whole .NET Core concept is new. The .NET Core 1.0 CLI is very new. Not only that, but .NET Core isn't as complete as the full .NET Framework 4.6. We're still exploring server-side graphics libraries. We're still exploring gaps between ASP.NET 4.6 and ASP.NET Core 1.0.

image

Which to choose?

To be clear, ASP.NET 4.6 is the more mature platform. It's battle-tested and released and available today. ASP.NET Core 1.0 is a 1.0 release that includes Web API and MVC but doesn't yet have SignalR or Web Pages. It doesn't yet support VB or F#. It will have these subsystems some day but not today.

We don't want anyone to think that ASP.NET Core 1.0 is the finish line. It's a new beginning and a fork in the road, but ASP.NET 4.6 continues on, released and fully supported. There's lots of great stuff coming, stay tuned!


Sponsor: Big thanks to Wiwet for sponsoring the feed this week. Build responsive ASP.NET web apps quickly and easily using C# or VB for any device in 1 minute. Wiwet ASP.Net templates are integrated into Visual Studio for ease of use. Get them now at Wiwet.com.

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Sponsored By
Hosting By
Dedicated Windows Server Hosting by ORCS Web
2016年1月20日 0:04:18 UTC
This is great news. Much clearer now!
Stuart Lang
2016年1月20日 0:04:24 UTC
Thank you guys, this is MUCH better and easier to explain.
Mohamed
2016年1月20日 0:05:48 UTC
This is cool and makes total sense, but for class library owners what's the impact (if any) to framework monikers?

A year ago you needed to target dnxcore50 for ASP.NET Core 1.0. Currently it's dotnet, and this is going to change soon to netstandard. Is this going to change again now?
2016年1月20日 0:10:25 UTC
"netstandard" is the way forward, Damien.
Scott Hanselman
2016年1月20日 0:11:01 UTC
I personally liked this change! One step closer to the perfect side.

However, it would have been nice to see it with a valid SemVer like 1.0.0. Not mucn different but it would make it easier to communicate I think.
2016年1月20日 0:11:01 UTC
I like the name scheme.

A small typo: "for a one major reasons" - fix to "reason".

Otherwise, great work!
2016年1月20日 0:13:08 UTC
Ofer, fixed, thanks!
Scott Hanselman
2016年1月20日 0:14:15 UTC
I thought the saying was "There are only two hard things in Computer Science: cache invalidation, naming things, and off-by-one errors."
2016年1月20日 0:14:26 UTC
Really nice.. clears up and shows that .NET Core is a all new from the ground up
Filipe Pessoa
2016年1月20日 0:14:52 UTC
Great, thanks for clarifying Scott!

It really does make all of this a little more straightforward.
2016年1月20日 0:16:08 UTC
Why not call it .net core 0.5? Call it 1.0 when you are done with pending stuff!
I think you guys knew from beginning that this is ground up. Why were you calling theses things as 5 and 7?
Hemant Sathe
2016年1月20日 0:19:02 UTC
Hemant - Because it IS 1.0 and it IS production ready. It's not at feature-parity with the 15 year old mature .NET "full" Framework, but it is NOT a 0.5 release.
Scott Hanselman
2016年1月20日 0:20:08 UTC
This is great. Should make searching a lot clearer. Thanks!
Blake Mumford
2016年1月20日 0:20:43 UTC
It's a great opportunity to think in a logo / branding.
What you think about Scott?
2016年1月20日 0:23:22 UTC
Much cleaner than the previous name, more distinct, and will definitely help to reduce the confusion between the .NET Framework 4.6 and .NET Core.
Matija
2016年1月20日 0:23:57 UTC
The new name is much better; good thing you changed it before the final release, too ;)

There are only two hard things in Computer Science: cache invalidation and naming things. - Phil Karlton


I'd argue there are a quite a few other hard things... multithreading is the first that comes to mind.
2016年1月20日 0:24:36 UTC
yum install dotnetcore? or yum install aspnetcore?
名前
メールアドレス gravatarアイコンを表示)
ホームページ
 
コメント(一部のHTMLは使用可能です:a@href@title, b, blockquote@cite, em, i, li, ol, pre, strike, strong, sub, super, u, ul@はattributeつまり属性を意味します。例えば、<a href="" title=""> or <blockquote cite="Scott">.などを使用することができます。)
コメントのプレビューを同時に表示

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.