Is the term Asp Net MVC correct?

MVC is a software design ( design pattern ) that separates the information representation from user interaction with it.

ASP.NET MVC is a lightweight and highly testable presentation framework that (like Web Forms-based applications) integrates with existing ASP.NET such as masters pages and association-based authentication. The MVC structure is defined in the System.Web.Mvc assembly.

ASP.NET MVC Framework Features

• Separation of application tasks (input logic, business logic and IU logic), testability and test-driven development (TDD). All core contracts in the MVC framework are interface-based and can be tested using dummy objects, which are simulated objects that mimic the behavior of the actual objects in the application. You can test the application drive without having to run the drivers in an ASP.NET process, which speeds up and flexes the unit test. You can use any unit test framework that is compatible with the .NET Framework.

• An extensible and connectable structure. The components of the ASP.NET MVC framework are designed to be easily overridden or customized. You can connect your own display engine, URL routing policy, action-method parameter serialization, and other components. The ASP.NET MVC framework also supports the use of the Dependency Injection (DI) and Inversion of Control (IOC) container models. DI allows you to inject objects into a class, rather than relying on the class to create the object. The IOC specifies that if an object requires another object, the first objects must obtain the second object from an outside source as a configuration file. This makes testing easier.

• Comprehensive support for ASP.NET routing, which is a powerful URL mapping component that allows you to develop applications that have comprehensive, searchable URLs. URLs do not need to include file name extensions and are designed to support URL naming standards that work well for SEO (Search Engine Optimization) and Representational State Transfer (REST) addressing.

• Support for using markup in ASP.NET (.aspx), user control (.ascx), and master page (.master files) markup files as display templates. You can use existing ASP.NET features with the ASP.NET MVC structure, such as nested master pages, inline expressions (<% =% >), declarative server controls, templates, data binding, location, and so on .

• Support for existing ASP.NET resources. The ASP.NET MVC framework enables the use of features such as forms authentication and Windows authentication, URL authorization, membership and roles, output and data caching, session and profile state management, health monitoring, provider architecture.

It is correct to use the term if you are using this Microsoft framework, otherwise (you are implementing the default in another language) you can only refer to as MVC .

Reference: Overview of ASP. NET MVC

Not correct .

It is correct to use ASP.Net MVC .

This is the name of a Microsoft technology. It is a proper name and should be spelled correctly. The name is one thing. It is correct to use to refer to this specific technology that is different from MVC, it is different from classic ASP.Net that uses WebForms and is mainly different from classic ASP that does not use .Net.

ASP (Active Server Pages) was a technology that Microsoft created to make web pages using an original Visual Basic variation.

When she created .Net, this framework that supports C # and VB.Net languages, among others, she also created a new version of this technology and called it ASP.Net. It's something quite different from the original ASP and you can use .Net languages.

Note that ASP is capitalized because it is an acronym. and .Net (it reads "dotnet") not because it is not an acronym (although Microsfot also uses .NET in several places, so this form is also correct). The name comes from networking, because at the time Microsoft wanted to baptize everything from "something" network point, to indicate that everything would be done to run on network. That's the way it is. Even Windows was called Windows.Net. But they gave up the idea and only a few things had this suffix. It's obvious that .Net would be the core Windows technology. But they realized it was an exaggeration.

Then Microsoft realized that a lot of people did not like ASP.Net and some people used the MVC standard. So she created another framework from scratch, completely different, using this design pattern and called it from ASP.Net MVC. For obvious reasons was included the acronym in the name (in capital, of course).

Initially it depended on some parts of ASP.Net that we often call classic to make sure it's the old one, although when we do not use MVC in the name, it's the one we're talking about. Although some people use it wrong.

I do not believe in programmers who can not use the name of the technology correctly. It may sound silly, but programming is detail. If the programmer can not know the name of the technology he is using, he will not know how to use it correctly. Until he changes his attitude. I do not trust you speak "delfi" instead of "delphi", which is the correct one. It's a proper name, you have to talk right. Either one is not curious and ignores something obvious and too easy, or knows and is stubborn and careless. Both are intrinsic personal traits that prevent her from evolving as a professional.

Today the ASP.Net Core (yes, one more confusion, but the initial name of the technology was worse ) which is a set of technologies that have evolved in relation to ASP.Net MVC (have been completely rewritten and there is total compatibility), does not depend on anything from the old. And this is important. Technology is reaching maturity.

You may find it confusing. And in fact Microsoft is not good at naming, or even versioning products. She tries to use criteria that only she understands is good and confuses people.

So, of course, it's okay to use this when you're using this technology . But it's wrong to call it just MVC because there are other MVC's, it's wrong to call ASP.Net only, worse still call ASP because it's another technology.

ASP.Net has become a legacy technology. Still supported, but no longer receive significant evolutions. It does not fit well in the current web environment. The full set of ASP.Net Core technologies work best for today's needs. And we should avoid even mixing them from now on.

Whoever wants to better understand technology, all fonts are available to do what you want in Github .