All geek questions in one place

ASP.NET 5 name confusion

If ASP.NET 5 is a new runtime that runs on both .NET Core and Full, then what should we call current ASP.NET or something that depends on System.Web when .NET 5 is released ? I believe ASP.NET 5 takes number 5 from the next version of .NET, which will continue to include and support System.Web. Perhaps classic ASP.NET?

@cecilphillip pointed out that the next version of .NET is 4.6, not 5. So, where did 5 come from?

Historically, ASP.NET versions have been the same as .NET, as described on this page :

  • ASP.NET 4.5.1 and Visual Studio 2013
    Provides information about ASP.NET objects in the .NET Framework 4.5.1 and Visual Studio 2013.
  • ASP.NET 4.5 and Visual Studio 2012
    Provides information about ASP.NET objects in the .NET Framework 4.5 and Visual Studio 2012 and Visual Studio Express 2012 for the Internet.
  • ASP.NET 4 and Visual Studio 2010
    Provides information about ASP.NET objects in the .NET Framework 4 and Visual Studio 2010 and Visual Web Developer 2010 Express.
  • ASP.NET 3.5 and Visual Studio 2008
    Provides a link to topics that describe ASP.NET features in the .NET Framework 3.5 and Visual Studio 2008 and Visual Web Developer 2008 Express Edition.
+6
source share
2 answers

ASP.NET version numbers are not tied to .NET Framework version numbers. They may have been the same historically, but this does not mean that there is a rule that they should continue to say the same thing, especially considering how out-of-band versions are used.

ASP.NET 5 is the fifth major release of ASP.NET, hence 5. ASP.NET 5 was previously called ASP.NET vNext.

The upcoming version of the .NET Framework is .NET 4.6. Obviously, Microsoft did not feel modified enough to ensure that the major version number jumps.

There is also a new type of infrastructure called .NET Core. I do not think that it will have traditional version numbers, since they consist of separate independent package versions. I saw him say that Microsoft plans to have a “basic level,” which is a set of specific versions of the packages that they certify that will work together.

+3
source

I wonder if you know the history of Python,

http://en.wikipedia.org/wiki/Python_(programming_language)

where 2. * never leaves (actively supported), and new releases from 3. *.

ASP.NET is on the same path where

  • Deprecated web applications (WebForms and MVC) that rely on System.Web will not disappear. If we look at classic ASP (more than 10 years), there are still sites using it.
  • Deprecated web applications (Web API and SignalR) will not disappear.
  • New web applications (purely based on the new ASP.NET 5 interfaces) will grow.

Therefore, Microsoft must support two main platforms (or battery life), aka

  • .NET Framework 4.6 (and future versions) to support legacy applications in the first place.
  • .NET Core 5 (and future versions) to support new applications with cross-platform features.

ASP.NET 5 is an application framework that, fortunately, can run on both the .NET Framework 4.6 and .NET Core 5.

Tons of sessions can be found at dotnetConf 2015 to cover these materials. Therefore, I hope that you can save some time on them.

For legacy applications, you can still call them,

  • ASP.NET 4 Applications
  • ASP.NET MVC 5 Applications
  • ASP.NET Web API 2 Applications

etc. based on different contexts.

+2
source

Source: https://habr.com/ru/post/985803/

More articles:


All Articles