Done. Now agent should target .NET Core 3.0 and .NET Standard 2.1, without that will not work.

PS. My orchestrator handled the change from .NET Core 2.2 to 3.0 without any problem.

How does this compare to my branch? https://github.com/ardalis/CleanArchitecture/tree/ardalis/net30update

Now that 3.0 is RTM, I suppose it makes sense to have master default to it, and to just tag 2.2 for those who will still want to use that. I could probably create a 2.2 Release as well. I just don't want to force all users to have to use 3.0 if they can't upgrade yet.

Answering your question. In ~80% this same code if we're speaking about migration from 2.2 to 3.0.
Differences:

• I keep IWebHostBuilder because I don't need a custom implementation of Autofac because initialization goes from Infrastructure. I learned from the migration of 150 services from Unity to Autofac that one project(eg. Infrastructure.Setup) should keep information about initialization because the client had 6 types of initializations(Web, API, ReadApi, NServiceBus, WCF, Tests - 100 lines avg. each initialization in one solution). Copy-paste approach was the tedious and error-prone, so generic initialization went to the shared library. Shared project(eg. Infrastructure.Setup) have only minimum information that needs to fill. In some rare cases executing assemblies fill container too but only by action method.
• Program.cs MVC methods changed to:

services.AddControllersWithViews().AddNewtonsoftJson();
services.AddRazorPages();

and

app.UseEndpoints(endpoints =>
{
	endpoints.MapDefaultControllerRoute();
	endpoints.MapRazorPages();
});

• DbContext implementation moved to Infrastructure.
• Swagger working :-)

Everything else it's only cleanup of references and targets. Projects have minimum information about custom deploy settings.

Good point, additional branch as 2.2 before migration to keep two versions until 3.1 LTS.