Dependency Injection too vague

[joshbinney]

Type of issue

Typo

Description

Hey, the dependency injection section is missing a lot of detail. How do we inject an EventProcessorClient? There are a lot of other clients too that aren't mentioned. If it is not possible to do so, please add that to the documentation.

Page URL

https://learn.microsoft.com/en-us/dotnet/api/overview/azure/messaging.eventhubs-readme?view=azure-dotnet#registering-with-aspnet-core-dependency-injection

Content source URL

https://github.com/Azure/azure-docs-sdk-dotnet/blob/master/api/overview/azure/latest/messaging.eventhubs-readme.md

Document Version Independent Id

7a8fbaaf-994b-eb9f-be4b-056f33556ffd

Article author

@azure-sdk

Metadata

• ID: bf82af3a-81e8-70f3-9c42-660b8481caf1
• Service: event-hubs

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[jsquire]

Thank you for your feedback, @joshbinney. You cannot inject an event processor-based type (including EventProcessorClient) nor the EventHubBufferedProducer by design, as these are intended to be directly instantiated, configured, and then explicitly managed by an application.

We'll look at getting the docs updated to clarify.

[joshbinney]

Thank you, appreciate the quick reply

…

On Wed, 18 Dec 2024, 6:23 am Jesse Squire, ***@***.***> wrote: Thank you for your feedback, @joshbinney <https://github.com/joshbinney>. You cannot inject an event processor-based type (including EventProcessorClient) nor the EventHubBufferedProducer by design, as these are intended to be directly instantiated, configured, and then explicitly managed by an application. We'll look at getting the docs updated to clarify. — Reply to this email directly, view it on GitHub <#47586 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALRBPVQH6DO2ZWYYVPC3UFL2GBMXZAVCNFSM6AAAAABTXJT2P6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBZGA4TONRXGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>