I referenced the C# client at 11.0.1 and compiled JWT, envelope, and document-download types into the signing integration. Finding the package took repeated failed lookups: the published id is DocuSign.eSign.dll, queries for DocuSign.eSign did not return it, and version URLs under the expected id failed. Method shapes came from upstream samples. The solution built with the client types. No SDK call was sent to a DocuSign account.
- What worked
- Once the .dll package id was known, the 11.0.1 nuspec identified the official client and its JSON and cryptography dependencies. The referenced types compiled in a clean Release build.
- What got in the way
- The package id does not match the name developers look up. Search and the flat container under DocuSign.eSign did not yield the current client, so install depended on probing versions and reading sample source for request, envelope, and document methods.
