Why should I migrate my .NET Framework applications to .NET Core/.NET 6?

-

The most famous project among the .NET platform was the now hated Asp.Net WebForms, which helped many companies on that time to migrate some legacy Windows Forms application to the Web platform, once the Visual Studio allowed developers to drag and drop web controls in visual design mode, a similar experience that took place for desktop applications. I know that feature usually did not generate the best HTML ever, but I think the idea was good in general and had its value at the beginning of it. The Asp.Net Web Forms had a not good performance in many cases, once everything was rendered in the backend, including the HTML, keeping the state using “tricks” with View State. The payload of each page could be enormous in many cases, but it was pretty easy to develop with.

The .NET Framework introduced the Asp.Net MVC project template in order to follow the good practices used in the rest of the market. It was a tremendous success because it was possible to separate responsibilities between the different layers of the application by default and the Visual Studio tools allowed us to easily create CRUD operations using the scaffold option, which creates all the necessary views, database commands using Entity Framework and the logic in the controllers without relevant effort. It was a lot of productive and everyone was convinced of its benefit comparison to Asp.Net Web Forms:

  • better performance
  • compliance with good practices of separation of concerns
  • More alignment with the concept of Web API for the upcoming boom of client-side libraries
  • Improvements in terms of testability
  • Security enhancements

The Asp.Net MVC project template had a huge impact on Web development among .NET developers once the majority of enterprise applications to this date still having many CRUD and repetitive operations. Additionally, the use of integration tests was already a popular practice at this point and the use of Controllers for handling the requests became the task much easier

Asp.Net Web API + Client-side libraries

Web development changed considerably in order to move the payload from the server to the client-side in every case it is possible. With applications being used by millions of users making constant requests, scalability became a key point and, in this context, the responsibility delegation to client/browser was definitely a good idea. The use of client-side libraries got pretty popular with Angular and React leading the market. In order to meet this demand, the creation of an application with only Web APIs in the backend and Angular/React projects in the frontend was a powerful option in order to keep the use of Controllers in the backend and meeting the requirements of the use of client-side to build Single Page Applications. Therefore, the Angular and React templates combined with the Asp.Net Web API project in the backend started being one of the most preferred options among .NET developers for Web development

Why should I migrate to .NET Core/.NET 6?

These are the reasons why it is valuable to move to .NET Core/.NET 6?

  1. There is no support anymore for really old versions of .NET Framework
  2. There are no updates anymore regarding Web Forms
  3. Probably, the maintenance of the project built in old versions of .NET Framework is costing more money once it is consuming more server resources
  4. NET Core and .NET 5 contain tons of improvements in terms of performance
  5. Improvements in terms of syntax and features in newer versions of Asp.Net and C#
  6. Better security is always a good point in newer technologies
  7. Over time, it is much harder to find professionals who are willing to working with old technologies. Everyone likes new technologies and it includes getting difficulties in the hiring process by the companies.
  8. The sooner the better for updating to the newer versions once as long as there is a delay in doing that, the jump will be too big causing possible instability problems.
  9. Opportunity to constantly review the projects to be sure they are following the best practices of software development.
  10. Stability is a good point here once newer versions always contain relevant updates and fix the legacy features.

Comments

Post a Comment

Popular posts from this blog

Email Sending through O365 using OAuth Protocol

-
  Microsoft Office365 EWS servers have been extended to support authorization via the industry-standard OAuth 2.0 protocol. Using OAUTH protocol, user can do authentication by Microsoft Web OAuth instead of inputting user and password directly in application Microsoft / Office 365 OAuth + EWS We can use the OAuth authentication service provided by Azure Active Directory to enable our application to connect with IMAP, POP or SMTP protocols to access Exchange Online in Office 365. To use OAuth with our application we need to register application on Azure Active directory and other steps also we need to do to get the access token back. Below are the steps   To use Microsoft/Office365 OAUTH in your application, you must create an application in  https://portal.azure.com . Sign into the Azure portal using either a work or school account or a personal Microsoft account. If your account gives you access to more than one tenant, select your account in the top right corn
Read more

IISRESET vs App Pool Recycling ?

-
Image
 I think most IIS administrators know IISRESET command, and why they use it. One of possible reasons can be to restart IIS services to initialize web applications, or to apply some changes of applications & IIS settings .There’re just a few conditions those need your IISRESET command. In most situations, you don’t need this. I have a concern if you always run this command for applying any changes, or release system resource – memory – regularly, or frequently. Because it’s much more cost than what you really need to take – there’re side effects Recycling App Pool’ has been introduced from IIS6 in Windows2003. It’s designed to restart only application pools(=worker processes). It can be done in a command prompt(run ‘IISAPP /?’ in a command prompt for details), as well as in the IIS manager What IISRESET does? When you run IISRESET, many things will happen. In order to understand them, I think I need to show you how IIS looks like – about IIS core components. The below shows you role
Read more

Deploy .Net6.0 Web api with docker

-
Image
  What is Docker? Docker is a containerization platform, meaning that it enables you to package your applications into images and run them as “containers” on any platform that can run Docker. It negates the classic: “It works on my computer” argument as Docker images contain everything needed for the app to run. Are Containers the same as Virtual Machines? They are similar, but not the same. In short: Virtual Machines provide OS Level Virtualization Containers provide App Level Virtualization This concept is depicted below: Why Would You Use it? In short you would use Docker, (and hence containers), for the following reasons: Portability.  As containers are self- contained  they can run on any platform that runs Docker, making them easy to stand up and run on a wide variety of platforms. Scalability.  With the use of additional “orchestration” you can spin up multiple container instances to support increased load. Performance.  Containers generally perform better than their VM counterp
Read more