Replies: 1 comment
-
Duplicate of #4952. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
According to the NuGet package, the
Microsoft.Extensions.Http.Resilience
supports .NET Framework 4.6.2 or later.And yet, when I update my project which multi-targets
net48
andnet8.0
to use this package, I receive a slew of almost-identical warnings:This is repeated for each of:
Each of these packages lists .NET Framework 4.6.2 as a target framework.
Are these packages "lying" about the frameworks they support? Or is Visual Studio now expecting a precise match between TFM and NuGet version, rather than a
>=
test?Reproduction Steps
Create a new console application.
Change the target framework to
net48
, as listed in the Target frameworks in SDK-style projects documentation.Add a reference to
Microsoft.Extensions.Http.Resilience
version 9.2.0.Expected behavior
Visual Studio should not generate any warnings for the reference.
Actual behavior
Visual Studio generates the 8 warnings listed in the description.
Regression?
No response
Known Workarounds
No response
Configuration
VS2022 Version 17.13.0
Windows 11 24H2
Other information
No response
Beta Was this translation helpful? Give feedback.
All reactions