Revert changes for net5 tfm

[sungam3r]

          > for some projects I've removed net5.0 tfm as it's [not supported anymore](https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core)

It should be reverted. It make no sence to require higher TFM in case no specific APIs are used from that TFM. Yes, net5 not supported anymore but this is story about runtime/end-applications but not about libraries. With such change as at picture above you make impossible for net5 apps to use this health check though healthcheck itself works perfectly targeted for net5.

Originally posted by @sungam3r in #2044 (comment)

[sungam3r]

ping @adamsitnik

[adamsitnik]

With such change as at picture above you make impossible for net5 apps to use this health check though healthcheck itself works perfectly targeted for net5.

But it's still targeting netstandard2.0, so .NET 5, .NET Core 3.1 and even 2.1 apps can still use it.

[sungam3r]

It's a question of another dimention. Look https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks/blob/master/src/HealthChecks.Uris/UriHealthCheck.cs#L41

[sungam3r]

One should not bump tfm requirements just because.

[adamsitnik]

Look

Thanks for pointing that out! 👍

One should not bump tfm requirements just because.

If we follow the .NET release schedule and use the same major version numbers, when should we drop non-supported TFMs?

[sungam3r]

No

[sungam3r]

"Not supported" is not applicable from api-set point of view.