.NET Framework Migration to .NET 8

[@petherpettersson6152]

Read this as DB migration, was thinking it was quite a lot of pre-talk. 🤣

[@seangwright]

Ah... OWIN and Katana. I don't miss those awkward years of .NET, but learning that technology made adopting aspnet core pretty easy.

[@BetrayedEnemy]

That was quick ! Thank you @CodeOpinion

[@gordondaniel]

Great video! It takes a talent to put such issue into a 10 minutes video. Almost like Scotty Kilmer with cars 😂 !!!

[@CodeOpinion]

Ha, never got that comparison but I'll take it!

[@connorradeloff5597]

Just letting you know that there's a very high-pitch ringing sound at around 5.5khz in the audio of this video, if you put the mp3 of this video into an online spectrum analyzer you can see it very clearly as a constant horizontal line. Great video!

[@CodeOpinion]

Interesting. Thanks for letting me know

[@PankajNikam]

Thank you for this video 💖

[@andreybiryulin7207]

Migrating AspNet WebApi2 controller to AspNetCore controllers is quite painful. Authorization migration was quite painful too. And also EF6 to EF Core requires a lot of runtime testing because EFCore8 still doesn't support some kinds of queries EF6 supports.

[@SteveNgaiCheeWeng]

example for query it doesn't support?

[@drleandrocorrea]

.NET upgrade assistant does an amazing job on updating those scary old .NET Framework .csproj files

[@joseville]

Does it convert them to SDK projects?

[@drleandrocorrea]

@@joseville yes

[@CodeOpinion]

I'm incredibly glad they simplified to the new SDK style.

[@matiascasag]

.NET Standard 2.0 works with .NET FW and .NET Core not the 2.1 version of Net Standard

[@CodeOpinion]

Correct. .NET Core 2.1

[@muhammadtariq8323]

Also your input about what are the best way to serve static (pre-compressed) files in .net rather then on the fly every time. Further, the convert razor pages / MVC to static pages as data changes not frequently on some pages.

[@rajnishthakur6930]

Hi @CodeOpenion currently, I am working with the same kind of project but facing a problem with OWIN layer migration as it's resulting in 404 error. Can you please guide what can be a possible reason? When I debugged found that http response object that contains response property get changed from (200 to 404) after passing invoke method of OWIN middleware.