If we use the Microsoft.Azure.EventHubs.Processor library with the .NET platform

Question

Context

We are currently using Microsoft.Azure.ServiceBus.EventProcessorHost to receive data from the Azure Event-Hub. We are working on the .NET framework , not the .NET Core .

This Microsoft announcement (published February 2, 2017) offers the new Microsoft.Azure.EventHubs.Processor - this is the way to go in the future, regardless of the .NET runtime used, because they will support a single code base.

At the same time, the official Microsoft Event-Hub examples , updated recently, still offer an older library (Microsoft.Azure.ServiceBus.EventProcessorHost) for the .NET framework.

Both libraries have been updated and developed since the announcement.

Question

Since we are in the .NET framework , which library should we use in the future?

Should we upgrade to the new Microsoft.Azure.EventHubs.Processor to benefit from the latest changes, improvements, and bug fixes? Or an old one that can accelerate?

The question also concerns beginners which library they should choose to get started with Azure Event-Hubs.

Answer 1

, Microsoft.Azure.EventHubs. :

• . , , , , MIT.
• .NET Standard. - .NET Core .NET, Event Hubs.
• , Microsoft . , , :
  • docs.microsoft.com . https://docs.microsoft.com/azure/event-hubs/event-hubs-dotnet-standard-getstarted-send
  • Microsoft , Azure . .. : https://blogs.msdn.microsoft.com/azureservicefabric/2018/03/14/service-fabric-is-going-open-source/
  • . Microsoft /legagcy, . https://azure.microsoft.com/blog/event-hubs-dotnet-standard-client-reaches-ga/