Deployment and redistribution of MailBee.NET Objects with your application
I'm going to distribute my application powered by MailBee.NET Objects. Which files should I include in my package?
- MailBee.NET.dll is the only mandatory file in most cases.
- If your application uses iCal and vCard functionality from ICalVCard.dll, you'll need to redistribute it as well.
- If you're using MailBee.BounceMail classes, you'll also need to supply bounce definition database which resides in BounceDatabase folder of MailBee.NET Objects installation. This database is a set of XML files. There are other options available: single xdb file or your own storage. See DeliveryStatusParser(byte)
topic for details.
- If you're using Ews component, add Exchange Web Services Managed API library, Microsoft.Exchange.WebServices.dll.
- If you're using MailBee.Pdf classes, add ITextSharp.dll and HtmlAgilityPack.dll assemblies.
DotNetOpenAuth.dll and Google APIs libraries (used for OAuth 2.0 authentication) are not included with MailBee.NET Objects setup but can be obtained with NuGet.
It's not required to register the .DLLs in GAC or anything like that. Just make sure they reside in the application folder, or in /bin folder in case of a web application. Placing in GAC, however, grants an assembly Full Trust level, which may be the desired behavior if you want to give such permissions to MailBee.NET.dll. For instance, to make use of S/MIME functions, Full Trust is required due to the need to make WinAPI calls. In case when the standard Trust Level of the application domain is lower than Full Trust, adding MailBee.NET.dll to GAC will be among possible solutions.
Send feedback to AfterLogic
Copyright © 2006-2017 AfterLogic Corporation. All rights reserved.