-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question]: Migration guidance for IHttpClientFactory and Microsoft.Extensions.Resilience #1788
Comments
Check out this discussion for links to the documentation for the new libraries, which are likely to be out of prerelease tomorrow with the release of .NET 8: #1657 Both extension libraries are maintained by the .NET team, so I would expect migration documentation to come from them rather than us. |
Also, Polly v8 can be used with the previous extensions as-is with no problem. |
Once the new Microsoft.Extensions.Http.Resilience comes out of pre-release mode, I plan to migrate one of my projects to it from the now deprecated version. Depending on how that goes, I might write up a migration doc. |
Makes sense. For some reason I didn't realize that the v7 types were all still included in v8. Thanks for the quick reply. |
This is my thinking as well. I think the migration guide should be handled by them. @kmcclellan could you create the issue in https://github.com/dotnet/extensions so this be can tracked there? |
What are you wanting to achieve?
I want to migrate to Polly V8, but I am using
Microsoft.Extensions.Http.Polly
in many places, which is now deprecated. The migration guide doesn't appear to have any guidance on this.What code or approach do you have so far?
The replacement for
Microsoft.Extensions.Http.Polly
(Microsoft.Extensions.Resilience.Http
) is still in prerelease as of now, so it looks like I need to wait before I can upgrade.Additional context
No response
The text was updated successfully, but these errors were encountered: