Untitled

[csportercom-blog]

C# to C++ Code Porting Control Now Fully Support Networking Functionality

What's New in this Release?

Aspose team is pleased to announce the release of Aspose.Email for .NET 19.1, This release includes few enhancements in API and overall functionality of the API has been improved as a result of several bug fixes. This release includes few enhancements to the API’s functionality. These enhancements include listing messages while working with Pop3Client, loading and saving of VCF contact and reading of OLM and MBX files. This release includes several improvements in term of bug fixes, such as improved working with EWSClient while UpdateItems, Improved formatting of HtmlBodyText in output, Improved working with loading EML, Improved working with date in header using MapiMessage to display in MHTML output, Improved working with ImapClient.ListMessagesByPage, MSG contact to MHT conversion is enhanced, Improved working with signed MSG, MailMessage to HTML conversion is enhanced, VCF to MSG conversion is enhanced, PST to MBOX conversion is enhanced and MSG to MHTML is enhanced The main bug fixes & improved features added in this release are listed below

Pop3Client.ListMessages taking too much time

Unable to update email using EWSClient.UpdateItems

Loading and saving VCF contact skips some information

No bullets added to the output of HtmlBodyText

MailMessage.load throwing exception with EML     Bug

Update date in header using MapiMessage to display in MHTML output

ImapClient.ListMessagesByPage retrieves last email even if the page does not exist

MSG contact to MHT conversion issue

MapiMessage.fromMailMessage throws exception

Issue while reading MBOX file

Empty body in a signed MSG

MailMessage to HTML conversion generates wrong HTML format

Issues with VCF to MSG Conversion

Issue with duplicate attachment after converting calendar mail

Folder Skipped While Converting PST to MBOX

MSG to MHTML - non-ASCII characters are transformed to question mark

The appointment content is improperly encoding

Issue while reading OLM File

MapiMessage.FromMailMessage throws Exception

Aspose.Email IgnoreSmtpAddressCheck does not allow %20 sequence

How to set MapiTask DateCompletion before Start Date

Unable to open EML file with MailMessage

Converting MSG to MHT throws exception

Newly added documentation pages and articles

Some new tips and articles have now been added into Aspose.Email for .NET documentation that may guide users briefly how to use Aspose.Email for performing different tasks like the followings.

Getting Total Number of Messages from MBox File

Export Microsoft Visio Drawing to PDF

Overview:Aspose.Email for .NET

Aspose.Email for .NET is a set of .net email components allowing developers to easily implement email functionality within their ASP.NET web applications, web services & Windows applications. It Supports Outlook PST, EML, MSG & MHT formats. It allows developers to work with SMTP, POP3, FTP & MS Exchange servers. It supports mail merge, iCalendar, customized header & body, header information, embedded files, Twitter & many more. It makes it easy to work with HTML or plain text emails & their attachments.

More about Aspose.Email for .NET

Homepage of Aspose.Email for .NET C#

Download Aspose.Email for .NET

Online documentation of Aspose.Email for .NET

[csportercom-blog]

csPorter Newsletter February 2019 is Here: Easily Port Complex C# Projects to C++

csPorter Newsletter for February 2019 has now been published. It includes information about easily porting complex C# projects to C++ with minimum manual efforts and automatic translation of C# language constructs to C++.   Users can now easily convert C# based source code applications and projects into native C++ equivalent. Control the translation of exact language constructs using global rules or via attributes placed in the C# code. It also allows reproducing even internal classes and routines in the same way as they are implemented in original code. csPorter for C++ not only converts C# projects to C++, but it also preserves API when doing so. It means the language constructs used in C# are translated into best matched ones available in C++. It offers posting control by the translation of exact language constructs either by using global rules or via attributes placed in the C# code. Such an approach allows not only executing ported code, but also using it from natural C++ perspective. This includes inheritance, type conversions, method overloads and so on.