We are pleased to announce the release of Aspose.Email for .NET 5.0.0. This month’s release brings improvements to the existing functionality of the API by introducing enhancements and fixing a number of bugs. For a complete list of public API changes, please visit our documentation article, Public API Changes in Aspose.Email 5.0.0. In case of any query/inquiry, please feel free to contact us over Aspose.Email forum.
Support for loading Appointments with Byte Order Mark (BOM) Characters
This month’s release provides support for loading appointments having Byte Order Mark (BOM) characters at their start. BOM use is optional and appears at the start of the text stream when used. Earlier, this was a non-supported appointment type by Aspsoe.Email but this month’s release now adds the capability to load such type of appointments for further processing and manipulation. The same Appointment class’s Load method can be used to load such appointments.
Support for Managing Password property of a PST
The PR_PST_PASSWORD property of a PST file represents the password protection of a PST file. Removal of this property cannot be achieved as other properties are removed from a message store. Instead, we need to set its value to zero (0) in order to get it removed. This month’s release introduces a new property for PST files, known as Store. It allows to access store properties of PST instead of MessageStoreProperties of PST for resetting the property. More Info
This month’s release also includes a number of bug fixes that further ads to the overall functionality of the API. Specifically, these include bug fixes related to:
- Text color issues while conversion of messages to MHTML
- Characters encoding issue while saving appointment files
- Issues related to exporting appointments to message format
- Exceptions raised such as MSG to XPS conversion, creating voting options using Exchange clients, interpreting messages as TNEF and conversion of some messages to TNEF