Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Is .NET Core == .NET Framework 5?

Tags:

.net

.net-core

I have been looking for books to study the latest .NET Framework. As far as I know .NET is up to 4.6 but ASP.NET is up to 5(Core)

Is .NET Core the name for .NET 5 or are we still currently at .NET 4.6?

like image 815
AnonDCX Avatar asked Dec 04 '16 04:12

AnonDCX


People also ask

Is .NET Framework 5 or core?

Net doesn't change the . Net Core architecture, but adds some additional benefits including Core Runtime & API Performance enhancement, and deployment flexibility. . Net 5 also supports some major sub-framework for desktop development like Entity Framework, GDI+, LINQ, and ADO.Net.

Is .NET Core and .NET Framework the same?

NET Core and . NET Framework is a platform for . NET applications on Windows whereas, NET Core is the latest version of the . NET Framework which is a cross-platform and open-source framework optimized for modern app needs and developer workflows.

Is there a .NET Core 5?

NET Core, . NET 5 is open-source and cross-platform. It provides high performance and allows side-by-side installation. In addition to the .

What framework version is .NET Core?

NET Framework is at version 4.8 and remains fully supported by Microsoft. In 2014, Microsoft introduced . NET Core as a cross-platform, open-source successor to .


2 Answers

To quote 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.

Update

On 7th of May 2019, Microsoft 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.
like image 171
Andrew Savinykh Avatar answered Sep 20 '22 07:09

Andrew Savinykh


For anyone ending up here after the fact, as of 6th May 2019, there is a new answer to what .net-5.0 is all about. In summary, .NET Core and .NET Framework are coming together as .NET 5 and there will be "just one .NET going forward".

We are also taking the opportunity to simplify naming. We thought that if there is only one .NET going forward, we don’t need a clarifying term like “Core”. The shorter name is a simplification and also communicates that .NET 5 has uniform capabilities and behaviors.

The original announcement and the new .NET schedule can be found on the .NET Blog, and it was also discussed at Build 2019 in a Scott Hanselman session (timestamp: 52:30) entitled ".NET Platform Overview and Roadmap".

like image 22
John Avatar answered Sep 19 '22 07:09

John