Skip to content
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

Open
kmcclellan opened this issue Nov 14, 2023 · 5 comments
Open

Migration guide for Microsoft.Extensions.Http.Polly #40841

kmcclellan opened this issue Nov 14, 2023 · 5 comments
Labels

Comments

@kmcclellan
Copy link

The Microsoft resilience documentation claims that Microsoft.Extensions.Http.Polly is superseded by Microsoft.Extensions.Http.Resilience. Is this true? Would be nice if there were a migration guide.

@RuntimeRascal
Copy link

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.

@cremor
Copy link

cremor commented May 10, 2024

@IEvangelist Should this issue be moved to dotnet/docs? Tagging you because you would be tagged for documentation issues on that page.

@IEvangelist
Copy link
Member

Hi everyone, yes... we need to write a guide. This should be transferred to docs. Thank you

@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label May 10, 2024
@IEvangelist IEvangelist transferred this issue from dotnet/extensions May 10, 2024
@IEvangelist
Copy link
Member

@timheuer is this something that the Upgrade Assistance is capable of migrating?

@timheuer
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants