Skip to content

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

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

Closed
JunTaoLuo opened this issue Sep 27, 2019 · 0 comments · Fixed by #15044
Closed
Assignees
Labels
breaking-change Indicates a .NET Core breaking change

Comments

@JunTaoLuo
Copy link

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

As part of making ASP.NET Core more pay for play, the ObjectPoolProvider was removed from the main set of dependencies. Specific components relying on ObjectPoolProvider now add it themselves.

If your component requires ObjectPoolProvider, it will be need to be added to your dependencies via the IServiceCollection.

For discussion, please use dotnet/aspnetcore#5944

Version introduced

3.0

Old behavior

WebHostBuilder provides ObjectPoolProvider by default in the DI container.

New behavior

WebHostBuilder no longer provides ObjectPoolProvider by default in the DI container.

Reason for change

This change was made to make ASP.NET Core more pay for play.

Recommended action

For anyone relying on ObjectPoolProvider, you should add them to your dependencies via the IServiceCollection.

Category

  • ASP.NET Core

Affected APIs

"Not detectable via API analysis"


Issue metadata

  • Issue type: breaking-change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Indicates a .NET Core breaking change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants