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.
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?
– Maniero
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.
– Randrade
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.
– Randrade
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.
– Maniero
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.
– Randrade
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.
– Randrade
"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?
– Maniero
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.
– Randrade
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
– Randrade
Devmedia articles often have a lot of wrong information.
– Maniero
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.
– Randrade