Upgrade to .NET Core 3.0 for the last fucking attempt #128
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Upgrade the entire micro-service platform to .NET Core 3.0. Cool!
Revert "Upgrade the entire micro-service platform to .NET Core 3.0. Cool!"
…e-to-3_0 Re-upgrade the platform to .NET Core 3.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrade to .NET Core 3.0 for the last fucking attempt. This is the last time I try to upgrade the platform to .NET Core 3.0.
And I was fucked by Microsoft. .NET Core 3.0 is very very fucking which caused us a lot of fucking code.
Fucking EF Core 3.0 migration management
You can not run
dotnet ef migrations add. I really don't know why. Fucking kidding me!Fucking EF Core 3.0 new feature
Now EF Core 3.0 disabled client-side evaluation. Which means many of our lambda expression failed.
dotnet/efcore#14935
So our logic requires refactoring! What the fuck! They can never imagine how much it costs to upgrade from 2.2 to 3.0!
Upgrading from 2.2 to 3.0 is almost like re-write the entire project.
Fucking JSON library
.NET Core 3.0 is forcing us to use their new fucking JSON library which is lacking features and will ruin our code logic.
There is a way to switch back to old JSON.NET but some features in the base class are still using the old logic and hard to change. Which cost some our or features stop working.
Fucking Azure DevOps
Azure DevOps can not build projects targeting .NET Core 3.0 by default. Fucking kidding me.
dotnet/core#2859
Fucking Azure App Service
Azure App Service does not support .NET Core without changing your deploy mode to SCD. Fucking kidding me.
https://github.com/aspnet/AspNetCore.Docs/blob/master/aspnetcore/migration/22-to-30.md#aspnet-core-30-not-currently-available-for-azure-app-service
Fucking performance
.NET Core 3.0 makes our project works extremely slow.
What the fucking wrong is that!?
Exclusion
.NET Core 3.0 is very fucking and hard to upgrade. Upgrading may cause you by fucked by your credit card. And you may work 996 and get in ICU.
We will keep this pull request open. But do NOT merge it until Microsoft fixed all those issues mentioned.