Azure Cosmos DB Table .NET API: Download and release notes
|Quickstart||Azure Cosmos DB: Build an app with .NET and the Table API|
|Tutorial||Azure Cosmos DB: Develop with the Table API in .NET|
|Current supported framework||Microsoft .NET Framework 4.5.1|
The .NET Framework SDK Microsoft.Azure.CosmosDB.Table is in maintenance mode and it will be deprecated soon. Please upgrade to the new .NET Standard library Microsoft.Azure.Cosmos.Table to continue to get the latest features supported by the Table API.
If you created a Table API account during the preview, please create a new Table API account to work with the generally available Table API SDKs.
- Bug fixes
- Bug fixes
- Added Multi-region write support
- Fixed NuGet package dependencies on Microsoft.Azure.DocumentDB, Microsoft.OData.Core, Microsoft.OData.Edm, Microsoft.Spatial
- Fixed NuGet package dependencies on Microsoft.Azure.Storage.Common and Microsoft.Azure.DocumentDB.
- Bug fixes on table serialization when JsonConvert.DefaultSettings are configured.
- Added validation for malformed ETAGs in Direct Mode.
- Fixed LINQ query bug in Gateway Mode.
- Synchronous APIs now run on the thread pool with SynchronizationContext.
- Add TableQueryMaxItemCount, TableQueryEnableScan, TableQueryMaxDegreeOfParallelism, and TableQueryContinuationTokenLimitInKb to TableRequestOptions
- Bug Fixes
- General availability release
- Initial preview release
Release and Retirement dates
Microsoft provides notification at least 12 months in advance of retiring an SDK in order to smooth the transition to a newer/supported version.
Microsoft.Azure.CosmosDB.Table library is currently available for .NET Framework only, and is in maintenance mode and will be deprecated soon. New features and functionalities and optimizations are only added to the .NET Standard library Microsoft.Azure.Cosmos.Table, as such it is recommended that you upgrade to Microsoft.Azure.Cosmos.Table.
The WindowsAzure.Storage-PremiumTable preview package has been deprecated. The WindowsAzure.Storage-PremiumTable SDK will be retired on November 15, 2018, at which time requests to the retired SDK will not be permitted.
|Version||Release Date||Retirement Date|
|2.1.2||September 16, 2019|
|2.1.0||January 22, 2019||April 01, 2020|
|2.0.0||September 26, 2018||March 01, 2020|
|1.1.3||July 17, 2018||December 01, 2019|
|1.1.1||March 26, 2018||December 01, 2019|
|1.1.0||February 21, 2018||December 01, 2019|
|1.0.0||November 15, 2017||November 15, 2019|
|0.9.0-preview||November 11, 2017||November 11, 2019|
If you get the error
Unable to resolve dependency 'Microsoft.Azure.Storage.Common'. Source(s) used: 'nuget.org', 'CliFallbackFolder', 'Microsoft Visual Studio Offline Packages', 'Microsoft Azure Service Fabric SDK'`
when attempting to use the Microsoft.Azure.CosmosDB.Table NuGet package, you have two options to fix the issue:
Use Package Manage Console to install the Microsoft.Azure.CosmosDB.Table package and its dependencies. To do this, type the following in the Package Manager Console for your solution.
Install-Package Microsoft.Azure.CosmosDB.Table -IncludePrerelease
Using your preferred NuGet package management tool, install the Microsoft.Azure.Storage.Common NuGet package before installing Microsoft.Azure.CosmosDB.Table.
How will I be notified of the retiring SDK?
Microsoft will provide 12 month's advance notice before the end of support of the retiring SDK to facilitate a smooth transition to a supported SDK. We'll notify you through various communication channels: the Azure portal, Azure updates, and direct communication to assigned service administrators.
Can I author applications by using a to-be-retired Azure Cosmos DB SDK during the 12-month period?
Yes, you'll be able to author, deploy, and modify applications by using the to-be-retired Azure Cosmos DB SDK during the 12-month notice period. We recommend that you migrate to a newer supported version of the Azure Cosmos DB SDK during the 12-month notice period, as appropriate.
After the retirement date, what happens to applications that use the unsupported Azure Cosmos DB SDK?
After the retirement date, Azure Cosmos DB will no longer make bug fixes, add new features, or provide support to the retired SDK versions. If you prefer not to upgrade, requests sent from the retired versions of the SDK will continue to be served by the Azure Cosmos DB service.
Which SDK versions will have the latest features and updates?
New features and updates will be added only to the latest minor version of the latest supported major SDK version. We recommend that you always use the latest version to take advantage of new features, performance improvements, and bug fixes. If you're using an old, non-retired version of the SDK, your requests to Azure Cosmos DB will still function, but you won't have access to any new capabilities.
What should I do if I can't update my application before a cutoff date?
We recommend that you upgrade to the latest SDK as early as possible. After an SDK is tagged for retirement, you'll have 12 months to update your application. If you're not able to update by the retirement date, requests sent from the retired versions of the SDK will continue to be served by Azure Cosmos DB, so your running applications will continue to function. But Azure Cosmos DB will no longer make bug fixes, add new features, or provide support to the retired SDK versions.
If you have a support plan and require technical support, contact us by filing a support ticket.
To learn more about the Azure Cosmos DB Table API, see Introduction to Azure Cosmos DB Table API.