The Azure SDK team is pleased to announce our December 2019 client library releases.
- Key Vault (Certificates)
To install any of our packages, please search for them via
Manage NuGet Packages... in Visual Studio (with
Include prerelease checked) or copy these commands into your terminal:
$> dotnet add package Azure.Storage.Blobs $> dotnet add package Azure.Storage.Blobs.Batch $> dotnet add package Azure.Storage.Queues $> dotnet add package Azure.Storage.Files.Shares $> dotnet add package Azure.Storage.Files.DataLake --version 12.0.0-preview.7 $> dotnet add package Azure.Security.KeyVault.Secrets $> dotnet add package Azure.Security.KeyVault.Key $> dotnet add package Azure.Security.KeyVault.Certificates --version 4.0.0-preview.7 $> dotnet add package Azure.Messaging.EventHubs --version 5.0.0-preview.6 $> dotnet add package Azure.Identity $> dotnet add package Azure.Data.AppConfiguration --version 1.0.0-preview.4 $> dotnet add package Azure.Cosmos --version 4.0.0-preview
If you have a bug or feature request for one of the libraries, please file an issue in our repo.
Detailed changelogs are linked from the Quick Links below. Here are some of the highlights:
- Added check to enforce TokenCredential is used only over HTTPS
- Support using SAS token from connection string
- Update return types of
Response<CloseHandlesResult>, respectively, in Files.Shares
- DataLake Preview 7
A large portion of the public API surface, including members and parameters, have had adjustments to their naming and organization in order to improve discoverability, provide better context to developers, and better conform to the Azure SDK Design Guidelines for .NET. For more details, please see the Event Hubs and Event Processor changelogs.
EventProcessorClienthas been moved into its own package and evolved into an opinionated implementation on top of Azure Storage Blobs. This is intended to offer a more streamlined developer experience for the majority of scenarios and allow developers to more easily take advantage of the processor.
A bug with the use of Azure.Identity credential scopes has been fixed; Azure identities should now allow for proper authorization with Event Hubs resources. (A community contribution, courtesy of albertodenatale)
EventHubProducerClienttypes are no longer bound to a partition; the partition and other attibutes may now be requested at the operation-level to allow for more granular control over behavior without the need to create multiple clients.
Events may now be read across all partitions of an Event Hub using the
ReadEventsmethod of the consumer client. This is intened for exploring Event Hubs and not recommended for production use; for production scenarios, please consider using the
EventProcessorClientas a more robust alternative.
The API for the
EventProcessorClienthas been revised, adopting an event-driven model that aligns to many of the .NET base class library types and reduces complexity when constructing the client.
View all the latest versions of .NET packages here.