azure-cosmos-dotnet-v3 | NET SDK for Azure Cosmos DB for the core SQL API | Azure library

You are correct that those samples might need polishing, the main difference is:

• GetDatabase just gets a proxy object, it does not mean the database actually exists. If you attempt an operation on a database that does not exist, for example, CreateContainer, it can fail with a 404.
• ReadAsync will read the DatabaseProperties and allow you obtain any information from there and also would succeed if the database actually exists. Does that guarantee that if I call CreateContainer right away it will succeed? No, because the database could have been deleted right in the middle.

So in summary, ReadAsync is good if you want to get any of the DatabaseProperties or if you want to for some reason verify the database exists.

Most common scenarios would just use GetDatabase because you are probably attempting operations down the chain (like creating a container or executing item level operations in some container in that database).

There is no equivalent class in Cosmos SDK 3.#. If you want to read/create item without partition key, you can use PartitionKey.None.

Example:

In your provided code, it seems like you're sending the partition key name "id" rather than the id of the item. It should look like:

I found the javascript equivalent for the etag and made the following fix:

Reference:

• https://github.com/Azure/azure-cosmos-dotnet-v3/issues/1551#issuecomment-634365001
• https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator#running-on-mac-or-linux

Following this guide, but the certificate needs to be a PFX, not CRT. It will ask you to set some password.

For example, I put it on a folder I can map to when booting Docker along with the code I wanted to run:

As per https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator#running-on-mac-or-linux, I used ipconfig and got my Windows IP.

In my case, I use one with the NET Core 3.1 SDK, the official one from https://docs.microsoft.com/en-us/dotnet/architecture/microservices/net-core-net-framework-containers/official-net-docker-images

I started the container with an interactive shell, and mapping localhost to the IP I got on Step 3. This let's you use localhost in the connection string.

docker run -v /c/DockerSample:/DockerSample --add-host="localhost:192.168.1.15" -it mcr.microsoft.com/dotnet/core/sdk:3.1 /bin/bash

And I'm also mounting the folder where I saved the project and the certificate I want to import. This is not required, but I'm not fluent on Docker to know if there is a better way to pass the certificate.

After the shell starts, I basically run the commands described in the Emulator doc and the certificate gets added.

The Docker container should now have the required Cert to connect to localhost and you should not need the HttpClientFactory.

NOTE: Also there is a bug tracking HttpClientFactory not being used everywhere that is the source of your error https://github.com/Azure/azure-cosmos-dotnet-v3/pull/1548

I tried the following code and it worked well for me. I was able to fetch the document details: