Microsoft.Extensions.Http.Resilience support for .NET Framework

[ayaya-dev]

Correct me if this is the wrong place. But since Microsoft.Extensions.Http.Resilience is a replacement for Microsoft.Extensions.Http.Polly we tried updating to it in our .NET Framework 4.8 project. However, this gives us a plethora of warnings for various packages.

Microsoft.Extensions.AmbientMetadata.Application 8.2.0 doesn't support net48 and has not been tested with it. Consider upgrading your TargetFramework to net6.0 or later. You may also set true in the project file to ignore this warning and attempt to run in this unsupported configuration at your own risk.

Maybe I'm missing something but the projects that get's the warning should support .NET 4.8 according to nuget.org.

Is Microsoft.Extensions.Http.Resilience supposed to support .NET Framework or is it just a mistake?

[RussKie]

No, it is not a mistake.

While the carried binaries compatible with the .NET Framework 4.6.2 onwards, Microsoft.Extensions.Http.Resilience (or any other Microsoft.Extensions.* packages for that matter) is not officially supported. The .NET Framework binaries are there to support Microsoft internal teams for the period of migration to .NET platform.

FWIW, Microsoft.Extensions.* packages originating from dotnet/runtime repo have the same warnings.

I understand this is probably not the answer you expected but this is the reality. That said, you can suppress the build warning <SuppressTfmSupportBuildWarnings>true</SuppressTfmSupportBuildWarnings> in your proj (or the global props) file and consume the package as before.

[KalleOlaviNiemitalo]

See also dotnet/extensions-samples#217 (comment) about the .NET Framework support difference between dotnet/runtime and dotnet/extensions.

[ayaya-dev]

Thanks for the clarification! We do not wish to enable SuppressTfmSupportBuildWarnings for all projects so I think we'll have to skip using the package. I do want to clarify though that the packages from dotnet/runtime does not have the same warning when using net48.

Maybe it should be documented somewhere for users that this is the way it is? At least I it made me confused since the warning says it doesn't support net48 while the package details says it does.

[KalleOlaviNiemitalo]

If you want to use the dotnet/extensions packages in the "unsupported configuration" and suppress the warnings for these packages only, you can add a Directory.Build.targets file that overrides the warning targets defined in the packages:

<Project>
  <Target Name="NETStandardCompatError_Microsoft_Extensions_AmbientMetadata_Application_net6_0" />
  <Target Name="NETStandardCompatError_Microsoft_Extensions_Compliance_Abstractions_net6_0" />
  <Target Name="NETStandardCompatError_Microsoft_Extensions_DependencyInjection_AutoActivation_net6_0" />
  <Target Name="NETStandardCompatError_Microsoft_Extensions_Diagnostics_ExceptionSummarization_net6_0" />
  <Target Name="NETStandardCompatError_Microsoft_Extensions_Http_Diagnostics_net6_0" />
  <Target Name="NETStandardCompatError_Microsoft_Extensions_Http_Resilience_net6_0" />
  <Target Name="NETStandardCompatError_Microsoft_Extensions_Resilience_net6_0" />
  <Target Name="NETStandardCompatError_Microsoft_Extensions_Telemetry_net6_0" />
  <Target Name="NETStandardCompatError_Microsoft_Extensions_Telemetry_Abstractions_net6_0" />
</Project>

No guarantees that this will keep working in future versions.

[KalleOlaviNiemitalo]

Maybe it should be documented somewhere for users that this is the way it is?

The README file of each package would be the obvious place to add this.

[joperezr]

FWIW, Microsoft.Extensions.* packages originating from dotnet/runtime repo have the same warnings.

Small clarification here, but packages from dotnet/runtime does support .NET Framework and don't have the same warnings. Their warnings, are when you try to run on out-of-support platforms, like .NET Core 2.0, 2.1, etc.