-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Migration guide for Microsoft.Extensions.Http.Polly
#40841
Comments
Any status updates on this. Just come across this need for a migration guide Today as VS gives a warning for using a deprecated Polly package. Clearly the API's are not the same so migrating is not so straight forward. |
@IEvangelist Should this issue be moved to dotnet/docs? Tagging you because you would be tagged for documentation issues on that page. |
Hi everyone, yes... we need to write a guide. This should be transferred to docs. Thank you |
@timheuer is this something that the Upgrade Assistance is capable of migrating? |
In theory yes! UA basically has project-based (e.g., move this whole thing from this version to this version) or feature-based (move this 'thing' in my app from X-Y -- like what we've been doing with Aspire). This I think would be a feature-based thing. |
The Microsoft resilience documentation claims that
Microsoft.Extensions.Http.Polly
is superseded byMicrosoft.Extensions.Http.Resilience
. Is this true? Would be nice if there were a migration guide.The text was updated successfully, but these errors were encountered: