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.
Any requests to Azure Cosmos DB using a retired SDK are rejected by the service.
|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.
1. How will customers be notified of the retiring SDK?
Microsoft will provide 12 month advance notification to the end of support of the retiring SDK in order to facilitate a smooth transition to a supported SDK. Further, customers will be notified through various communication channels – Azure Management Portal, Developer Center, blog post, and direct communication to assigned service administrators.
2. Can customers author applications using a "to-be" retired Azure Cosmos DB SDK during the 12 month period?
Yes, customers will have full access to author, deploy and modify applications using the "to-be" retired Azure Cosmos DB SDK during the 12 month grace period. During the 12 month grace period, customers are advised to migrate to a newer supported version of Azure Cosmos DB SDK as appropriate.
3. Can customers author and modify applications using a retired Azure Cosmos DB SDK after the 12 month notification period?
After the 12 month notification period, the SDK will be retired. Any access to Azure Cosmos DB by an applications using a retired SDK will not be permitted by the Azure Cosmos DB platform. Further, Microsoft will not provide customer support on the retired SDK.
4. What happens to Customer’s running applications that are using unsupported Azure Cosmos DB SDK version?
Any attempts made to connect to the Azure Cosmos DB service with a retired SDK version will be rejected.
5. Will new features and functionality be applied to all non-retired SDKs?
New features and functionality will only be added to new versions. If you are using an old, non-retired, version of the SDK your requests to Azure Cosmos DB will still function as previous but you will not have access to any new capabilities.
6. What should I do if I cannot update my application before a cut-off date?
We recommend that you upgrade to the latest SDK as early as possible. Once an SDK has been tagged for retirement you will have 12 months to update your application. If, for whatever reason, you cannot complete your application update within this timeframe then please contact the Cosmos DB Team and request their assistance before the cutoff date.
To learn more about the Azure Cosmos DB Table API, see Introduction to Azure Cosmos DB Table API.