We are pleased to announce the release of Aspose.Email for .NET 17.12. This release brings exciting feature of support for .NET Standard 2.0 (.NET Core) for our users. We have also merged Aspose.Email APIs for Xamarin platform in this month’s release. For a detailed note on what is new and fixed, please visit the release notes section of API documentation for Aspose.Email for .NET.
Support for .NET Standard 2.0
Starting from 17.12 release, the API now includes .NET Standard 2.0 (.NET Core). It has full functionality of standard .NET Framework except the following limitations:
- Email.Clients.ActiveSync.TransportLayer namespace is not available
- Email.Windows namespace is not available
- Email.Printing namespace is not available
- Linked images into message body in both RTF as well as HTML format are not supported
- It also has no functionality of Signing or Encrypting/Decrypting messages
- Email under .NET Core will work only with servers that implement at least TLS 1.0. Some servers (like Gmail) support both SSL and TLS. Aspose.Email can force them to use TLS.
Merged Xamarin APIs
Starting from this release, Aspose.Email for Android via Xamarin, Aspose.Email for iOS via Xamarin and Aspose.Email for Mac via Xamarin have become part of Aspose.Email for .NET. There are no breaking changes.
This release also includes several improvements in terms of bug fixes which further add to the overall stability of the API. These are related to various API functionality and include:
- Processing of encrypted messages
- Email messages to MHTML
- Rendering of hyperlinks to HTML during conversion
- Timezone changes during conversion of EML to MSG
- Exceptions while converting messages to MSG and ICS
- Loss of formatting during messages conversion to XPS
The following API resources can be of help to you in getting started with Aspose.Email API.