Yes - but we don't have any timelines yet. It turns this involves quite a bit of non-trivial work.
It turns this involves quite a bit of non-trivial work.
@aliuy I'm curious about that.
since incorporating DocumentDB and this SDK in to our codebase, we've hit a wall resulting from Issue #118 (we can't include a class library that has the SDK as a dependency as a dependency of our API app). One way I could have gotten around this was by having the source code to step through, and or, creating my own build. We're still without solution.
I'm not sure what's non-trivial about this (@aliuy) , but it seems imperative and probably a huge benefit to the DocumentDB product offering that the library source be opened. Would very much appreciate it.
DocumentDB itself is already kind of a blackbox but when you add the SDK on top of it, troubleshooting becomes a nightmare. This is no mere issue you need to figure out something.
Feature request asked on uservoice, consider upvoting
https://feedback.azure.com/forums/263030-documentdb/suggestions/18902368-opensource-documentdb-net-sdk
Hi DocumentDB team. Any update on the time lines for this?
Well looks like java is more trivial than c#, since the cosmosdb java sdk source code was open sourced. Dam the c# code is either a mess or is just easy to program in java.
Ping. @ausfeldt
The original request is from 2016.
It's really difficult to help with this, if code is not opensource.
There's a new version 3 of the .NET SDK for Cosmos DB now that's fully open source: https://github.com/Azure/azure-cosmos-dotnet-v3
@manigandham is right. It's been already open source. Therefore, I'm closing this issue.
Most helpful comment
@aliuy I'm curious about that.