There have been quite a few upgades to aspNetMime since our v2 release. Just a few of these upgrades are listed below.
aspNetMime runs under all releases of .NET.
S/Mime Parsing Support
aspNetMime also supports parsing S/Mime documents to allow you to securely extract data from S/Mime formatted content.
The new MimeToHtml class allows you to easily convert a Mime message to a Html document or string for display in a browser. Allow aspNetMime to handle converting embedded images, to extracted images, and handle all the attachment and image link conversions, to preserve the format of the message.
aspNetMime is Writable
aspNetMime is writable. This allows you to read in an existing Mime document, or create your own, and modify it as required. You can then output it back to the file system, a stream, string, or a byte array.
Added the MimeReader Class
The MimeReader class, allows you to read the Mime messages in a forward looking manner. This allows for faster parsing, and lower memory footprint. It is especially helpful, when you need to extract large attachments from a message, without incurring extra CPU cycles.
Added Static MimePart.Create(…) methods
These methods allow you to easily create, and add Mime parts to a Mime message from byte arrays, files, streams or strings.
Easily parse the header content and lines from documents using the HeaderCollection.Parse(…) methods, making all data in the headers easily accessible.
Easier support for modifying existing MIME documents
Besides being able to easily add additional parts, attachments, and images to a Mime message, you can easily append both plain text, and Html content to Mime parts, and allow aspNetMime to handle all of the complicated encoding.
Easier Searching for parts.
New methods allow you easily and quickly find more parts of the message. These methods include FindByExtension, GetByConentId,GetByContentLocation, or by ContentType.
RFC 2231 Support
Expanded support for non-ASCII charactersets found in parameters.
Expanded the internal MBX support by aspNetMime to parse MBX files.
Added and exposed additional methods for extracting InLine content-disposition types.
Force Garbage Collection
Exposed the functionality for developers to force Garbage Collection on the MimeReader class.
Added the ability to allow the developer to calculated GMT Offsets.
TNEF (winmail.data) RTF Support
Added the capability for aspNetMime to find and extract RTF data created by Outlook.
Expanded the support for determining different properties on collections of headers.
Expanded the support for saving individual parts off of the MimeReader class.
Expanded the capability of aspNetMime to recognize Windows specific charactersets that are non-RFC standard.
Added support for aspNetMime to find and extract TNEF (winmail.dat) parts. aspNetMime can also find attachments found within these parts.
Be sure to see a more complete list of the aspNetMime features over at the aspNetMime Product Page.
When upgrading to v3 of aspNetMime, there are a few small, but important, breaking changes.
With v3, we did away with digitally signed license files, and went to license keys. This will make it easier on customers when moving their applications.
The following methods went away:
These methods were replaced by the single
method, that simply loads the license key. For more information on how licensing works, visit our License Page.
Parsing MBX Files
Originally, when parsing MBX files, aspNetMime would create a calculated filename, and set it on the MimeMessage object. This behavior went away. Due to edge cases, the filename is no longer set, as it had the possibility of changing the underlying message characteristics in edge cases.
The RawText property is now null on the multi-part part. To get the RawText value, iterate over the multi-part children and combine their RawText values. This was done to decrease the memory footprint of large emails.
The EmailAddress value no longer returns the “<” and the “>” before and after the actual EmailAddress value.