The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
So I decided to upgrade a .NET Core 2.1 project to a .NET Core 2.2 project, after all what harm can it do?
A LOT APPARENTLY!
First, the build breaks.
Read some Scott Hanselman blog and I need to use the .NET Core Tool Installer in my build to install the .NET Core 2.2.100 SDK.
Done and on to Azure!
Except the site went down...
Turn on all logging I can find, but nothing!
I turn on detailed information in the browser in the web config, because I had absolutely nothing to go on (at this point the whole world can read my errors).
And there it is, a nice error "Handler "aspNetCore" has a bad module "AspNetCoreModuleV2" in its module list"
Do some additional reading and I can't make any sense of it.
Decide to try a completely new ASP.NET Core 2.2 project and immediately release it to Azure, same error.
WTF MICROSOFT IF EVEN YOUR DEFAULT TEMPLATE DOESN'T WORK HOW AM I SUPPOSED TO MAKE IT WORK!?
I made the only fix I could find... Revert to .NET Core 2.1...
(I just found out the "old" handler is AspNetCoreModule, perhaps it would've worked if I used that with 2.2?)
That's working to throw your work down the drain
Usually, I wouldn't mind all that much, except I wanted to go to bed about an hour ago
At least the site is up and running again
MS is putting out a lot of rubbish lately. I was trying to get my feet wet in UWP yesterday. The default Class library and Application projects wouldn't even compile properly at first. It would give me the most obscure compilation errors and send me off to a googling spree. Had to turn off Native compilation, randomly updated some nuget references, did some random nuget restore commands, and finally got these very basic projects compiling. I'm seriously starting considering jumping ship.
I rarely have that problem, they work most of the time, although I guess I've only used Web API lately.
I am missing a lot of .NET Core templates though (like Azure WebJobs or Functions).
And the templates they do have are often grossly outdated.
For example, I know their templates still used Bower long after Bower was considered obsolete (even by Bower's creator himself).