I recently migrated an old dotnet project to dotnet 3.1. Here are somt
Was it worth it?
Calculate Statistics old vs new versiom
And by default json models are returning camelCase to change to PascalCase if you are using that in you frontend layer
Now, if you are dealing with older version and want to migrate to dotnet core 3.1 then fasten your seatbelts your are up for the ride.
You have to change how session and cookies work, some razor extensions, return type of controller functions, inject your configuration to every controller, modify your appSettings, convert your global.acsx to Startup.cs and list goes on..
Now to question to ask yourself
Is it worth it?
How much bigger the project is? if you have more than 100 controllers I personally won't recommend it if it isn't critical or you don't have proper plan and bandwidth for it.
Was it worth it?
Calculate Statistics old vs new versiom
Should You Migrate to Dotnet core 3.1?
That really depends on what project you have in hand. if you are dealing with dotnet core project. That should be easy; You already should have startup class. Dependency injection and other pipelines configured. All you have to do is change target framework to 3.1
<TargetFramework>netcoreapp3.1</TargetFramework>
And by default json models are returning camelCase to change to PascalCase if you are using that in you frontend layer
services.AddControllersWithViews()
.AddJsonOptions(opt => opt.JsonSerializerOptions.PropertyNamingPolicy = null);
Now, if you are dealing with older version and want to migrate to dotnet core 3.1 then fasten your seatbelts your are up for the ride.
You have to change how session and cookies work, some razor extensions, return type of controller functions, inject your configuration to every controller, modify your appSettings, convert your global.acsx to Startup.cs and list goes on..
Now to question to ask yourself
Is it worth it?
How much bigger the project is? if you have more than 100 controllers I personally won't recommend it if it isn't critical or you don't have proper plan and bandwidth for it.
No comments:
Post a Comment