What is ASP.NET vNext? What is the correct name?

Asked

Viewed 1,634 times

21

Okay, I know that ASP.NET vNext is the new version of ASP.NET being released by Microsoft in 2015 and that brings big changes changing the way of working various things. This vNext name was used as the working name.

Initially I had the idea that this would be ASP.NET based on Webforms in its version 5 since the last one was 4. And ASP.NET MVC would be 6 since the last version was 5. In fact its version seems to be 6.0.0.

But I have seen dissonant information. I see the term ASP.NET 5 being used for MVC. And I’ve read that the old ASP.NET is pretty much abandoned and would actually be called ASP.NET 4.6 adjusting to . Net as a whole.

This would mean that the term MVC would be set aside since it would become the main web framework supported by Microsoft? And in fact although MVC is version 6, it is what is called ASP.NET 5?

What is the correct nomenclature of each of these two web frameworks in the new version? There is a canonical and authoritative reference that demonstrates this with clarity and reliability? (to make it clear that I don’t want opinions)

Webapi is now bundled with ASP.NET MVC. This means that this term disappears, that is, there will not be a Webapi 3?

Change something else about this?

This is important not only for me to know but also for us to use the tag correct here on the site.

Today none of this matters more, even though the question is still relevant to understanding how the name was conceived. The name ASP.NET 5 is now used for the new version, which is Core, but loses this nomenclature.

asp.net-mvc asp.net asp.net-web-api asp.net-core nomenclature

  • It’s MS being MS, makes a complex engineering product and can’t give a clear name to things. You know that Windows 7 is not version 7.x, right?

  • That really is a very confusing term. I know that ASP.Net 5 includes MVC 6 and the Web API in a single programming framework. But there are contradictory sources.

  • On the website of microsoft informs that to have reference on ASP.Net 5 must access the site http://www.asp.net/vnext, which indicates, by the link, that the vNext would be ASP.Net 5.

  • But that vNext name will disappear. I am understanding that ASP.Net MVC 6 will actually be called ASP.Net 5 and ASP.Net "classic" which would be 5 will actually be called ASP.Net 4.6, as I said in the question. But this is my understanding, I don’t know if it’s right.

  • The most concrete information I found was on this link http://www.asp.net/vnext/overview/aspnet-vnext which shows a series of articles about ASP.Net 5, and of course MS Connect() and Channel9, which explains a little more.

  • I also understood this, but I believe that the term vNext will "popularize" and this will make it difficult to use other terms, because in Channel9 they use this term until today.

  • "ASP.NET 5 is a significant redesign of ASP.NET. This topic introduces the new Concepts in ASP.NET 5 and explains how they help you develop Modern web apps." It doesn’t say that it is a redesign of MVC. But all understanding is that this is it. But the classic ASP.Net, as it turns out?

  • In my view, they are apparently "forcing" the use of it. One proof of this was leaving the Open-Source project, leading people to be more interested in analyzing and contributing.

  • I found an article in Devmedia speaking: "One of the first aspects to be highlighted was the definition of a unified programming model for the construction of websites and services. Mechanisms such as ASP.NET MVC, ASP.NET Web Forms and Web API have been placed side by side, with this grouping of technologies being called "MVC 6"." Full article: http://www.devmedia.com.br/novidades-do-asp-net-vnext-e-do-visual-studio/31166#ixzz3SrNs1wkL

  • Devmedia articles often have a lot of wrong information.

  • Yes, but at the end some references on the microsoft site, which help to reach their own conclusion. But also does not have a concrete definition.

Show 6 more comments

2 answers

16


What is ASP.Net vNext?

A part of you replied. It would be the initial working name of the new architectural model of ASP.NET, but it was a nickname that lasted a short time. Scott Hanselman, one of those responsible for the project, declared the names ASP.NET vNext and ASP.NET 5 dead here. The correct name for the set of architecture, tools and methodology is ASP.NET Core, starting in version 1.0.

But I have seen dissonant information. I see the term ASP.Net 5 being used for MVC. And I’ve read that the old ASP.Net is pretty much abandoned and would actually be called ASP.Net 4.6 fitting the . Net name as a whole. This would mean that the term MVC would be set aside since it would become the main web framework supported by Microsoft?

Kind of. The support continues, but in a discouraged way, in order to meet legacy systems, as is customary for technology suppliers. The idea is that the term MVC and others, such as the Web API, are implicit in the pattern of ASP.NET Core projects. Microsoft has unified features to simplify design standards and keep architecture more succinct.

And in fact even though MVC is version 6, it’s what’s being called ASP.Net 5?

These are two different things. The standard of MVC architecture would actually be going into its 6th incarnation. The standard of ASP.NET would be going to version 5 taking as standard this version 6 of MVC as architectural standard of projects, plus the unification of the Web API, REST Framework made for ASP.NET.

From the link I quoted, Hanselman argues that keeping a name like "ASP.NET 5" would give the feeling of eclipsing the ". NET Framework 4.6" in update and importance, besides suggesting that it would be a natural continuation of the product (which is not true) then the solution found was to standardize all the classifications for "Core" starting in version 1.0, and with this, the specification of a "MVC 6"followed the same path, being part of the ASP.NET Core 1.0 architecture.

What is the correct nomenclature of each of these two frameworks web in the new version? There is a canonical and authoritative reference that demonstrates this with clarity and reliability?

That reference came out only recently. Is this post here, where it is explained that some nomenclatures will no longer be used and that ASP.NET Core 1.0 needs to be seen as another product, and not exactly as a continuation of ASP.NET 4.6, as was previously expected to be.

Webapi is now bundled with ASP.Net MVC. This means that this term disappears, that is, there will not be a Webapi 3?

Not exactly. The Web API is now part of ASP.NET 5. If it is going to have its own control it is something that until the date of this answer we do not have yet.

The term disappears, but the Web API concept is maintained as the REST API solution of ASP.NET Core 1.0.

Change something else about this?

Dependency injections become part of the design standard of ASP.NET Core 1.0. It has also been incorporated into the architectural model the concept of Middleware, existing in other frameworks of other languages, and the concept of Request Features, that works together with the injections of dependencies and that, incidentally, we put in a framework who proudly contribute a little earlier.

  • I don’t know if it’s going to be outdated. I’d have to turn it around and change everything. It is still lacking a clearer reference, not because of you, and I think it is the only thing that can have the need to be improved when it can. The answer is good and I think it helps those who are confused, like me. Certainly fulfilled the goal of giving answers without opinion. This document from Guthrie was the one that got me confused because before it seemed to be something else, but of course what he did was make it a little bit clearer what was not.

  • 1

    In fact this organizational imprecision is part of the reorganization of this part of Microsoft. As they were a set of things changed in a very short time (for the size of the company and the teams), the teams have not yet had the availability to document everything. As soon as the correct references come out I will definitely be reviewing the answer.

  • 1

    Probably, at the right time, I will ask the question at the goal about the use of tag, but if you have any suggestions... I think the "classic" ASP.Net continues with the [tag:Asp.net], the "old" MVC continues with its tags simple or with the version number and this new MVC should use [tag:Asp.net-5]. At least I think it would be my initial idea.

  • @bigown I agree with your suggestion.

  • You think you can upgrade with Core now so I can accept?

  • That’s right. Come on.

  • I think you have it all now. That answer has changed quite a bit.

Show 2 more comments

6

What is ASP.NET vNext?

It’s nothing but codename for the next version of Asp.net in development. Let’s say, if today we have Aspnet 5 version in production, vNext may be Asp.net 6. see Wiki.

See this quote from an article by Carolyn Van Slyck (free translation):

vNext is Microsoft’s term for the next version of . NET which is based on its new OSS compiler (Roslyn). It includes both good and old . NET and ASP.NET. The goal is to make . NET development easier, truly cross-platform and cloud friendly. Source: link

What in fact was set aside in the Aspnet vNext is the webform application plattaform, since this type of application tends to be slower and testing tasks become unnecessarily difficult to do.

An important point is that the compiler you see being developed in vNext whose codename Roslyn, this compiler does not support webform, however, it will be possible to use webforms in the next versions of Aspnet, since when compiling, the developer changes "Roslyn" to the CODEDOM current compiler in production. See article by Jonathan Allen.

  • Although the answer does provide something conclusive I think it provided relevant information to clarify the question.

  • @bigown I still left as wiki to rightly make it clear that is an answer deserves to be improved under various visiting points.. I had this question about the term Asp.Net vNext and I came to think that it was a new one, but it’s actually just a code name of the future platform under development..

  • the vNext itself I understand.

Browser other questions tagged asp.net-mvc asp.net asp.net-web-api asp.net-core nomenclature

You are not signed in. Login or sign up in order to post.