I know that .NET Core 3.1 is followed by .NET 5 (this is by itself .net core).
I also know that .NET 4.8 is the last windows only (non .net core) framework.
So I think that ASP.NET MVC 5, ASP.NET Core MVC 5 are both the same. Is that correct?
7
-
5Not at all. ASP.NET MVC 5 runs on .net framework, which is essentially a discontinued product line. All new development should be on .net 5/6.Tanveer Badar– Tanveer Badar2021-11-26 08:48:26 +00:00Commented Nov 26, 2021 at 8:48
-
But isn't .NET 4.8 the final windows only (non .net core) framework?variable– variable2021-11-26 08:50:03 +00:00Commented Nov 26, 2021 at 8:50
-
1.NET Framework 4.8 is the final windows-only framework, yes. You're missing the word Framework there. See here. To reiterate what Tanveer said, .NET Framework is effectively discontinued, and .NET Core has become .NET 5, .NET 6, and so on.ProgrammingLlama– ProgrammingLlama2021-11-26 08:51:09 +00:00Commented Nov 26, 2021 at 8:51
-
What is confusing me is that - since you are saying that .NET core has become .NET 5, then why is .NET 5 MVC and .NET 5 Core MVC different?variable– variable2021-11-26 09:05:25 +00:00Commented Nov 26, 2021 at 9:05
-
1ASP.Net MVC 5 runs on .Net Framework 4.8 - ASP.Net Core 5 (which includes all the MVC and Web API bits) runs on .Net 5 which is the version after .Net Core 3 (there was no .Net Core 4)phuzi– phuzi2021-11-26 09:13:18 +00:00Commented Nov 26, 2021 at 9:13
|
Show 2 more comments
2 Answers
https://en.wikipedia.org/wiki/ASP.NET_MVC
ASP.NET MVC 1.0 was released on 13 March 2009, not part of the .NET Framework, running on top of ASP.NET, which was then part of .NET Framework 3.5.
MVC's version did not correspond to .NET Framework/ASP.NET versioning. MVC went through version 2, 3 and 4 and ASP.NET MVC 5 was released on 17 October 2013. Meanwhile the .NET Framework went from 3.5 to 4.7, now 4.8 but will never reach a higher major version.
Then .NET Core started under the working title "vNext". It was .NET Core 1, then 2, then 3. .NET Core includes ASP.NET Core, which included ASP.NET Core MVC. This versioned along with its framework.
Now to prevent confusion, they didn't want to name the fourth version of .NET Core as 4, because that'd conflict (not on a filesystem level, but in the heads of developers) with .NET Framework 4. So they unified .NET Framework and .NET Core, and called it .NET 5.
.NET 5 includes ASP.NET Core 5, which includes ASP.NET Core MVC 5, which is not the same as ASP.NET MVC 5.
The old .NET Framework (currently 4.8) and ASP.NET MVC 5.2.7 are considered finished. Maybe they'll receive security patches, but you shouldn't do new development in it, and skip tutorials that mention it.
11 Comments
phuzi
As ever, Microsoft has confused a lot of people with the naming and numbering of the .Net platform and ASP.Net.
CodeCaster
@phuzi yeah they should've started with .NET Core 6 to prevent any confusion. Then we'd have questions like "Where is .NET Core 4.8?"... :P
variable
I get it now, I got mixed up with the number 5 (.NET 5 and MVC 5)
phuzi
No, not exactly. There is no ASP.Net Core MVC 5! It's just ASP.NET Core 5 (there is no MVC in the name, it just includes MVC and Web API and Razor Pages and all the other ASP.Net stuff)
phuzi
It would really help if it could be "ASP.Net Core $verison MVC" although this doesn't help when you're not discussing a specific version.
|
- There are several difference between ASP.NET Core 5 and ASP.NET MVC 5 in the solution structure. The ASP.NET Core is a composable framework for implementing web and cloud based applications.
- ASP .NET MVC 5 helps to choose the MVC or Web API and we can able to choose both while creating a web application. But in Core we can able to choose single-aligned web stack for MVC nad Web API.
- The file structure are varies between them. the ASP.NET MVC 5 concicts of web.config, Global.asax files. But the Core does not contain these files instead it contains appsettings.json.
- And the ASP .NET Core does not need IIS for hosting since it is to be cross-platform and it is self hosted.
- In ASP.NET Core applications, dependency injection is inbuilt and no set up is needed for DI. But in ASP.NET MVC we want to use saparate DI container and then build up the project to use DI.
