Hy devs! should I go for .net mvc or .net core mvc?

Question

current I work on webforms and had a strong understanding of c# so what should I do my ultimate goal is to upgrade my skills from asp.net to .net core

Amit Mohanty · Answer

The choice between .NET MVC and .NET Core MVC depends on several factors, including your specific requirements, project goals, and technical considerations. .NET MVC: .NET MVC (also known as ASP.NET MVC) is built on the full .NET Framework. It has been around for a longer time and is a mature framework with extensive documentation and community support. It is suitable for applications that target the full .NET Framework and may require compatibility with legacy systems. If you have existing .NET Framework code or libraries that you want to leverage, .NET MVC might be the better choice. .NET Core MVC: .NET Core MVC is part of the newer, cross-platform .NET Core framework (now known as .NET 5+). It offers improved performance, scalability, and modularity compared to .NET MVC. .NET Core MVC is the recommended choice for new projects, especially those targeting multiple platforms (Windows, macOS, Linux). If you're interested in leveraging modern development practices and taking advantage of the latest features and performance improvements, .NET Core MVC is the way to go. Ultimately, it's worth considering the long-term viability and support for each framework. Microsoft has been actively promoting .NET Core and encouraging developers to migrate from the full .NET Framework. As of .NET 5, Microsoft has unified the platforms under the .NET umbrella, so going forward, .NET Core MVC (now just .NET MVC) will be the primary focus for new features and improvements. If you're starting a new project, I would recommend choosing .NET Core MVC unless you have specific reasons to use the full .NET Framework. Keep in mind that the decision also depends on factors such as team expertise, project requirements, and ecosystem compatibility.

Jignesh Kumar · Answer

Hello, It's depend on various factors such as your project requirements, target platforms, and future scalability needs. Here's a breakdown to help you make an informed decision: If you are starting your project from scratch then you should go with .net core mvc. .NET MVC: Older technology: It is stable and widely adopted. Windows-focused: application run on Windows servers. Legacy applications: If you have existing applications built on the .NET Framework, sticking with .NET MVC may be a more seamless transition. .NET Core MVC: Modern and cross-platform: .you can build applications that run on Windows, macOS, or Linux. Performance and scalability: .NET Core is optimized for high performance, and it offers better scalability compared to .NET MVC. Cloud-native: Your application in cloud environments like Azure or AWS, .NET Core is a good fit.

Mahesh Chand · Answer

.NET Core MVP of course. You always want to keep upgrading. Cheers!

Deepak Rawat · Answer

HI Dharm, Transitioning from ASP.NET Web Forms to ASP.NET Core may require some adjustments in your development approach and mindset. Be prepared to embrace new paradigms and practices in web development, such as dependency injection, cross-platform development, and containerization. Practice regularly and seek out real-world projects to gain confidence and mastery in ASP.NET Core.

Sam Hobbs · Answer

Choose an ASP.NET Core UI | Microsoft Learn https://learn.microsoft.com/en-us/aspnet/core/tutorials/choose-web-ui?view=aspnetcore-7.0 There is ASP.NET Core Razor Pages and ASP.NET Core MVC. Choosing which one to use is not clear. I am not sure but I think that ASP.NET Core MVC is considered appropriate for large professional sites but that is not certain. In my opinon at least, and I am not as experienced as others here, you should choose either one of the ASP.NET Core technologies. I am reading the book Pro ASP.NET Core 6 by Adam Freeman. I have gotten through the first part that describes creation of a website. That part does not explain things as much as I want, I am hoping that the remainder of the book explains things better. The author does respond to questions if you have a good question.

Hy devs! should I go for .net mvc or .net core mvc?

Answers (5)