cdean's account

Thank you Duo_Liang

I am looking for developer documentation that shows similar usage as CodeShare for this version.
The code I wrote works on the sandbox.esign server but I need use an older version of the eSign server.  
I want to make sure the calls I am making are "backward compatible" or if I need to change my implementation.

When I run the .NET SDK and REST API eSign code on the sandbox everything works.
The same code hangs when I try to run on our older eSign server.
 

Thank you, Duo_Liang

This should work.
I agree with you that the SDK is a bit tricky.

I've started using the REST API as it appears to work better regardless of version.
One issue I have with the REST API is that I need to convert JSON objects to Document Packages, etc. depending on the Response payload I'm trying to retrieve.
I don't want to really create models on my end to deserialize these objects.
The SDK is easier to use but is not as reliable as I get exceptions depending on the version I've used versus the version of the server I'm retrieving from.

Thanks for your help.
I'll let you know how 11.15 does....
FYI, I am now retrieving from an on-prem eSign server with version 7.2 that was just brought online today. :)

Whether I use 11.12 or 11.15 SDK on eSign server version 6.2 or 7.2 respectively, they both return the following exception when trying to draft a package OR any eSign SDK call:

15:29:47.382: Silanis.ESL.SDK.EslServerException: Could not upload documents to package.
                                                                      Exception: The remote server returned an error: (400) Bad Request.
                                                                      HTTP POST on URI https://<new 7.2 eSign on-prem server>/a/packages/WPq_qYyxLacEdaN_U8ifG9f-MLQ=/documents.
Optional details: 
System.Net.WebException: The remote server returned an error: (400) Bad Request.
   at System.Net.HttpWebRequest.GetResponse()
   at Silanis.ESL.SDK.Internal.HttpMethods.MultipartPostHttp(String apiToken, String path, Byte[] content, String boundary, AuthHeaderGenerator authHeaderGen)

Here is the code snippet of interest prior to the exception:

DocumentPackage draftDocumentPackage = PackageBuilder
                .NewPackageNamed(Path.GetFileNameWithoutExtension(pdfFile))
                .WithSigner(SignerBuilder
                            .NewSignerWithEmail(drow["_EmailAddress"])
                            .WithFirstName(drow["_FirstName"])
                            .WithLastName(drow["_LastName"]))
                .WithDocument(DocumentBuilder
                            .NewDocumentNamed(Path.GetFileNameWithoutExtension(pdfFile))
                            .WithId(drow["DocID"])
                            .WithDescription("Document with applied layout description.")
                            .FromFile(pdfFile))
                .Build();

                try {
                    PackageId draftPackageId = OneSpanClient.CreatePackage(draftDocumentPackage);  <--- exception thrown here
                 }
                catch (EslServerException ex) {
                    throw new EslServerException($"{ex.Message}", {ex.ServerError}, {ex});
                }

FYI, I also tested the REST API sample code to create a draft package on both our 7.2 on-prem eSign server and the OneSpan eSign sandbox server.
Without any changes, the 7.2 returns bad request while the sandbox creates the draft package and returns a package id.

Using our on-prem 7.2 server URL and changing the code as you suggested resulted in the following error:

Silanis.ESL.SDK.EslServerException: Could not create a new package one step. Exception: The remote server returned an error: (400) Bad Request. 

It appears there were no change to the outcome using the OneStep call.