For anyone considering upgrading to ASP.NET Core 3.0
-
I've been tasked with upgrading one of our web apps. It's currently implemented using ASP.NET Core 2.2 and we want to upgrade it to ASP.NET Core 3.0. I've upgraded many web apps previously and thought 'How hard can it be?' Well, I've spent the last two days getting it to compile and run. There's quite a few changes that are necessary in the assembly references, nuget packages and middleware that all need to be updated to work. I'd recommend spending some time reading some of the docs before plowing ahead and migrating your own projects. Also, you might find that some of your 3rd-party references won't work as they haven't been updated to support ASP.NET Core 3.0 (as we've found with one of ours). But hey it's all good fun :-D
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
I've been tasked with upgrading one of our web apps. It's currently implemented using ASP.NET Core 2.2 and we want to upgrade it to ASP.NET Core 3.0. I've upgraded many web apps previously and thought 'How hard can it be?' Well, I've spent the last two days getting it to compile and run. There's quite a few changes that are necessary in the assembly references, nuget packages and middleware that all need to be updated to work. I'd recommend spending some time reading some of the docs before plowing ahead and migrating your own projects. Also, you might find that some of your 3rd-party references won't work as they haven't been updated to support ASP.NET Core 3.0 (as we've found with one of ours). But hey it's all good fun :-D
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
3.0? 3.1 mate. 3.0 isn't an LTS offering.
-
I've been tasked with upgrading one of our web apps. It's currently implemented using ASP.NET Core 2.2 and we want to upgrade it to ASP.NET Core 3.0. I've upgraded many web apps previously and thought 'How hard can it be?' Well, I've spent the last two days getting it to compile and run. There's quite a few changes that are necessary in the assembly references, nuget packages and middleware that all need to be updated to work. I'd recommend spending some time reading some of the docs before plowing ahead and migrating your own projects. Also, you might find that some of your 3rd-party references won't work as they haven't been updated to support ASP.NET Core 3.0 (as we've found with one of ours). But hey it's all good fun :-D
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
Marc had a post about this recently: [The Lounge](https://www.codeproject.com/Messages/5692038/NET-Core-2-2-vs-NET-Core-3-1.aspx)
-
I've been tasked with upgrading one of our web apps. It's currently implemented using ASP.NET Core 2.2 and we want to upgrade it to ASP.NET Core 3.0. I've upgraded many web apps previously and thought 'How hard can it be?' Well, I've spent the last two days getting it to compile and run. There's quite a few changes that are necessary in the assembly references, nuget packages and middleware that all need to be updated to work. I'd recommend spending some time reading some of the docs before plowing ahead and migrating your own projects. Also, you might find that some of your 3rd-party references won't work as they haven't been updated to support ASP.NET Core 3.0 (as we've found with one of ours). But hey it's all good fun :-D
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
The removal of UseWebpackDevMiddleware made me weep.
cheers Chris Maunder
-
3.0? 3.1 mate. 3.0 isn't an LTS offering.
I'm upgrading to 3.0 first, then immediately upgrading to 3.1. Several articles I read stated that the migration path is easier if going to 3.0 first (and getting all the hard work out the way) before upgrading to 3.1.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter