We had a lot of pain upgrading to .NET core 3.0 and 3.1, there were some subtle breaking changes (like dotnet build doing a restore whereas it didn't before, ca

We had a lot of pain upgrading to .NET core 3.0 and 3.1, there were some subtle breaking changes (like dotnet build doing a restore whereas it didn't before, causing nasty runtime issues with platform dependent dependencies like SqlClient). If you haven't done the upgrade yet, plan plenty of time for it, and smoke test the heck out of it before you go live. Also ensure you're on the latest (1.1.1) version of SqlClient if you use SQL Server.