most of the changes are in program, and startup and package (nuget). just make a new 3.1 project and copy the file contents of these. add any packages you use to the template project first. check the docs of you packs to see if the updates have any changes
for startup.
I agree with you, since there are many complications to apply changes on the same solution. In addition of this, I think it's better to make it now and not later on, specially if the solution does not use a large number of dependencies and is going to grow
up in the future.
If I was in place of you then I would have starting this by making a new project in ASP.NET Core 3.1 and then transferring my old website to it one part at a time. Moreover ASP.NET Core 3.1 has a new feature of
Endpoint Routing which is a new thing to look for. The rest things are not that much important, I think you will not have to do much changes to make your project work in 3.1.
Helping you always. Don't forget to click "Mark as Answer" on the post that helped you.
♠ ASP.NET Core Tutorials → Start from the Beginning and become an Expert in 30 days time ♠
Member
4 Points
14 Posts
Migrate Asp.Net Core 2.1 to 3.1
Jan 02, 2020 06:41 AM|krrishbiju|LINK
Hi ,
Please help me on this,
I want to migrate my WebApi project from Asp.Net Core 2.1 to 3.1.
Please give me the instruction and guideline to set up through VS Code.
Regards,
Biju
Participant
1968 Points
1026 Posts
MVP
Re: Migrate Asp.Net Core 2.1 to 3.1
Jan 02, 2020 11:27 AM|maherjendoubi|LINK
Hi,
First, I recommend you migrate from 2.1 to 2.2 then from 2.2 to 3.0. The last step from 3.0 to 3.1 is very easy.
https://docs.microsoft.com/en-us/aspnet/core/migration/22-to-30?view=aspnetcore-3.1&tabs=visual-studio
Best regards,
Maher
Blog : https://maherjendoubi.io
All-Star
58194 Points
15658 Posts
Re: Migrate Asp.Net Core 2.1 to 3.1
Jan 02, 2020 03:16 PM|bruce (sqlwork.com)|LINK
most of the changes are in program, and startup and package (nuget). just make a new 3.1 project and copy the file contents of these. add any packages you use to the template project first. check the docs of you packs to see if the updates have any changes for startup.
None
0 Points
4 Posts
Re: Migrate Asp.Net Core 2.1 to 3.1
Mar 04, 2020 06:54 AM|AL.H|LINK
I agree with you, since there are many complications to apply changes on the same solution. In addition of this, I think it's better to make it now and not later on, specially if the solution does not use a large number of dependencies and is going to grow up in the future.
Participant
1253 Points
935 Posts
Re: Migrate Asp.Net Core 2.1 to 3.1
Mar 04, 2020 11:30 AM|yogyogi|LINK
If I was in place of you then I would have starting this by making a new project in ASP.NET Core 3.1 and then transferring my old website to it one part at a time. Moreover ASP.NET Core 3.1 has a new feature of Endpoint Routing which is a new thing to look for. The rest things are not that much important, I think you will not have to do much changes to make your project work in 3.1.
♠ ASP.NET Core Tutorials → Start from the Beginning and become an Expert in 30 days time ♠