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

Free Support Forum - aspose.com

Standardization of the API

Hi team,

We have been using your other APIs as well such as Word and Tasks. These have standard classes format to load or create new documents. However, the Aspose.email library is different in some cases. For example, why is there MailMessage.Load used or why is there MapiMessage.FromMailMessage or MapiMessage.FromFile being used? Like other APIs , we expect that these classes can be provided with constructors that can specify if its a new object from raw data or from existing mailmessage in case of mapimessage.

Though it is not necessary, but still we expect standardization across all your APIs and its always according to user’s expectation of usage. Hope someone can look into this.

Hi Acton,

Thank you for writing to Aspose Support team.

We have discussed this issue with our product team. This will be a big change and may need time for modification of the existing MailMessage, MapiMessage and any other similar APIs. We’ll update you here once we have some information about this requirement.