Closed aspnet4you closed 6 years ago
To add more, everything works great locally and I can view data in CosmosDB Emulator.
The issue is solved. I signed up for incorrect resource on Azure. It is working fine after I changed to Cosmos DB with SQL API. Initially, I was using Cosmos DB for Mongo DB!
Thanks for updating the issue. Glad you got it figured out.
This may not be a bug with ElCamino.AspNet.Identity.DocumentDB which is what I am using to interface with Azure CosmosDB. I am able to create dabase and collection on the fly and I am able to add/update items just fine. However, when I go to Azure and try to see the data in Data Explorer I get error saying {"code":500,"body":"Object reference not set to an instance of an object."}.
Anyone encountered this problem?
I think it has to do with Azure interface but I suspect if ElCamino.AspNet.Identity.DocumentDB is out of sync with Azure on data layout. I am doing a POC and ElCamino saved me time. Hope I don't have to reinvent my own documentdb repository myself!
I would appreciate your feedback.
Thanks, Prodip