Skip to content

ObjectPoolProvider removed from the default set of dependencies added in the WebHostBuilder #336

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

Open
davidfowl opened this issue Jan 9, 2019 · 0 comments
Labels
3.0.0 Announcements related to ASP.NET Core 3.0 Announcement Breaking change Documented The breaking change has been published to the .NET Core docs Migrated
Milestone

Comments

@davidfowl
Copy link
Member

davidfowl commented Jan 9, 2019

As part of making ASP.NET Core more pay for play, we moved the ObjectPoolProvider out of the main set of dependencies to the specific components that were using them.

If you were relying on the ObjectPoolProvider being available by default, you should add them to your dependencies via the IServiceCollection.

For discussion, please use dotnet/aspnetcore#5944

[This announcement has been migrated to: dotnet/docs#14736]

@davidfowl davidfowl added Announcement Breaking change 3.0.0 Announcements related to ASP.NET Core 3.0 labels Jan 9, 2019
@davidfowl davidfowl added this to the 3.0.0 milestone Jan 9, 2019
@aspnet aspnet locked and limited conversation to collaborators Jan 9, 2019
@JunTaoLuo JunTaoLuo removed their assignment Sep 27, 2019
@scottaddie scottaddie added the Documented The breaking change has been published to the .NET Core docs label Dec 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
3.0.0 Announcements related to ASP.NET Core 3.0 Announcement Breaking change Documented The breaking change has been published to the .NET Core docs Migrated
Projects
None yet
Development

No branches or pull requests

3 participants