We're sorry AsposeCloud doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.cloud

Word Document Processing Solution Aspose.Words Cloud SDK for .NET C# with strong name references


I’ve added a reference in the nuget package manager to Aspose.Storage-Cloud and Aspose.Words-Cloud.

However these references are not strong named and therefore do not load from our solution. Do you have any versions of these available which have a strong name?

Thank you


Thanks for your inquiry. I am afraid we do not have a strong named version of SDK and Storage DLLs. You may get Aspose.Words for Cloud SDK and Aspose.Storage for Cloud code from following GitHub repositories and amend as per your need for strong named DLLs.

Thank you,

Building these myself with strong name has resolved the issue.

Looking at this guide https://docs.aspose.cloud/display/wordscloud/Working+with+Mail+Merge. In the C# example it mentions Common.BASEPATH. Can you please clarify what Common.BASEPATH is supposed to be?

Edit: After some experimenting http://api.aspose.cloud/v2 seems to work as a value for this. Is this correct?

Is it possible to download the sample xml file and word doc file form this example? I tried to create my own templates based on the screenshots in the document. When I try to do the mail merge I get a return of Internal Server Error. This also happens if I try it on https://apireference.aspose.cloud/words/#/MailMerge/ExecuteMailMerge. When I check the Aspose SaaS activity log tells me it failed because “Input string not in the correct format” Am I doing something wrong here?

MergeTest.zip (55.0 KB)


Thanks for your inquiry.

Please note http://api.aspose.cloud/v1.1 is stable BaseProductURI, http://api.aspose.cloud/v2 is not stable yet, we are working on it.

You can download examples resource files from GitHub repository as well. Hopefully it will help you to accomplish the task.


Just an update, we have recently released API Version V4.0. It is better than older versions in terms of memory management and API structure. It is recommended to use the latest API Version. Let us know if you need any further help in this regard.