.net - .NET Core == .NET Framework 5 吗？

Question

我一直在寻找书籍来研究最新的 .NET Framework。据我所知 .NET 最高 4.6 但 ASP.NET 最高 5(Core)

.NET Core 是 .NET 5 的名称还是我们目前仍处于 .NET 4.6？

Answer 1

报价 Scott Hansleman :

Naming is hard.

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.

更新

2019 年 5 月 7 日，微软 announced .NET 5

Today, we’re announcing that the next release after .NET Core 3.0 will be .NET 5. This will be the next big release in the .NET family.

There will be just one .NET going forward, and you will be able to use it to target Windows, Linux, macOS, iOS, Android, tvOS, watchOS and WebAssembly and more.

.NET 5 = .NET Core vNext

.NET 5 is the next step forward with .NET Core. The project aims to improve .NET in a few key ways:

• Produce a single .NET runtime and framework that can be used everywhere and that has uniform runtime behaviors and developer
  experiences.
• Expand the capabilities of .NET by taking the best of .NET Core, .NET Framework, Xamarin and Mono.
• Build that product out of a single code-base that developers (Microsoft and the community) can work on and expand together and that improves all scenarios.