.NET Standard 2 support dropped

[markgould]

Is there a reason .NET Standard support was dropped in 5.0.1? (A major breaking change)

I have some sites that have to integrate with some full framework dlls, so they're .NET 4.7.2 ASP.NET Core projects which supports .NET Standard 2.0.

[AndrewTriesToCode]

hi @markgould

You are correct, in 5.0.1 when adding ASP.NET Core 3.1.1 support I also changed how the ASP.NET Core 2 support works by targeting netcoreapp2.1 instead of netstandard2.0. I did this mainly for consistency and easier maintenance. I intended to do it as part of 5.0 alongside other breaking changes. The January .NET Core updates came out very shortly after the 5.0 release so I took the opportunity to include this change. I think I will update the changeling to reflect this. .NET Framework compatibility hasn't been a priority, but maybe I should reconsider.

However I also tried to factor out anything needing ASP.NET Core from Finbuckle.MultiTenant.Core so that it could still target netstandard2.0. That gives you stores, strategies, and other basics. It lacks the strategies other items that are ASP.NET Core specific because those are in Finbuckle.MultiTenant.AspNetCore (i.e. anything that relies on HttpContext). This also includes the middleware which normally ties the strategy and stores together in an application.

It should be entirely possible to just reference Finbuckle.MultiTenant.Core from .NET Framework and use the basics. You might have to use the strategy and stores "manually" in doing so.

As an aside I also plan to support non-web scenarios in the next release via the new Host mechanism in .NET Core. I'm not sure if .NET Framework supports that or not--I'll have to check.

Some general background for anyone reading this:

• ASP.NET Core 1 was pretty much all .NET Standard
• ASP.NET Core 2 moved away from that and made it a little bit harder to write netstandard libraries for it, but it was possible to reference the specific ASP.NET Core packages you needed as they themselves were netstandard targets.
• ASP.NET Core 3 basically made it impossible (can't write a netstandard library which reference key ASP.NET Core 3 types like HttpContext)

[markgould]

Hi @achandlerwhite - thanks for the quick response, as always.

I'm planning on abstracting the pieces that rely on the full framework into a gRPC server, that way I can make the web project .NET Core 3 and keep current. So hopefully this shouldn't end up being an issue.

Appreciate the explanation!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.