How do I know what Cosmos SDK version was used to build the Cosmos Session Provider

Question

I'm getting emails saying Microsoft is retiring version 2.x of the Azure Cosmos DB .NET SDK, and I'll need to update your SDK to version 3.x. The thing is I just use the Microsoft.AspNet.SessionState.CosmosDBSessionStateProviderAsync Nuget package Version 2.0.0 released June 15th 2023.

How do I determine what version of the SDK my nuget package was built with?

Will I need to download the git repo, Cosmos SDK V3, and build locally?

Or is this some type of configuration issue with the Cosmos DB in my Azure portal and has nothing to do with my app?

Thank you

John

Answer 1

@John Love Thank you for reaching out.

Correct, seems like you have received an email stating that "On August 31, 2024, the Azure Cosmos DB .NET SDK v2.x will be retired; the SDK and all applications using the SDK will continue to function; Azure Cosmos DB will simply cease to provide further maintenance and support for this SDK. We recommend migrating to the latest version of the .NET SDK v3 SDK."

Version 3 of the Azure Cosmos DB .NET SDK includes updated features and improved performance. We recommend following the instructions to migrate to Azure Cosmos DB .NET SDK version 3.

Ref: https://www.nuget.org/packages/Microsoft.AspNet.SessionState.CosmosDBSessionStateProviderAsync/

https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/sdk-dotnet-v2

Regards,

Oury

Answer 2

Oury,

After reading into your answer more completely, I realize you did answer my question. I guess I was looking for a direct yes/no on the CosmosDBSessionStateProviderAsync 2.0 being compatible. To satisfy my need for absolute certainty, I went searching and confirmed that my current version 1.1.0 of the CosmosDBSessionStateProviderAsync was built using the Microsoft.Azure.DocumentDB library which is deprecated.

I've also confirmed the version 2.0.0 of the CosmosDBSessionStateProviderAsync nuget package was built using the updated Microsoft.Azure.Cosmos library version 3 mentioned in the email advisory.

So in the end, a simple NuGet upgrade in my project is all that is required.

Thank you for the help

regards,

John