On the question of complexity, the listed should not be compared with one parameter.You know, you know, it's a thing that treats one class of technology and that makes it easy to compare.To figure this out, we have to go back to the past.ASP was first. It was a "slightly subdirected php-cheek from Microsoft," where the html and code were blended, but there was already a strict typology and the possibility of connecting COM-components.This has opened up a great deal of opportunities to post the websites with active content of technology server-side, because the JS was at this point very well conceived only to draw snowflies on the front page between December and March.Then, as the ASP abrreviat has already been known to the audience (and Microsoft is very fond of the three-block abreviations) ASP appeared. NETThis was a huge step forward that allowed NET Framework to be applied on the Web server. The "possibility" here means the possibilities of languages (C#, VB.NET, and it seems F# - and they're all in an intermediate byte-code, which was done with NET runtime. But since the NET Framework (versions 1, 2, 3, 3.5, 4, 4.5, 4.51, 4.52, 4.6, 4.7 and 4.8) was only under the vindu, it was nailed to IIS and Microsoft Server, which, of course, caused ironic laughter in all bearded linux-admins.At the same time, ASP.NET MVC emerged, which identified the application of the Model-View-Sontroller template in ASP.NET. In fact, instead of a randomly grouped code, it was suggested that the code should be divided into essentially Model, View or Controller.NET Core was born in order to become a paid-up. Who works the same way on both vinda and the linux. It's a huge freymvork, of scale comparable to Spring' from the Java world. Its part relevant to WEB is named ASP.NET Core. It had the possibility of using the MVC template, which was likely to imply ASP.NET Core MVC.Because it's boring to write a lot of abstracts, names have narrowed down, for example, from ASP.NET Core MVC to NET Core MVC and, in fact, who's in the middle.In fact, there are:♪ NET Core is the whole frimevork.ASP. NET Core is part of the fraimvor buried under WEB.ASP. NET Core MVC is part of the foam box stored under WEB, using the MVC templateTherefore, in returning to the question, the comparison should be based on such a scheme:There is ASP or ASP in the name of technology. NET? If so, then this technology has something to do with WEB. If it's just "ASP" - it's likely NET's just forgotten to sign 'cause ASP technology is very old and it's no longer in use.Is there a Core in the name of technology? If so, the technology is cross-splatform and is based on the foil of NET Core. If there is a Framework in the name of technology or simply no Core word - it is likely that there is a NET Framefork that only operates WindowsIs there a MVC in the name of technology? If yes, the model-View-Controller division template is applied, if not, to the extent that it is not. Or cut down some of the abbreviations, considering everyone's gonna figure it out.So the answer to you. current The question (and prior to the questioning, you mentioned the use of the MVC template) as follows:| Название технологии | WEB или общего назначения? | Кроссплатформенная? |
| | | |
| ASP.NET Core | WEB | да |
| | | |
| .NET Core | общего назначения | да |
| | | |
| ASP.NET? | WEB | нет, только Windows |
Is that clearer?