.NET Core Edition

MailBee.NET library is also available in the version which is compatible with .NET Standard 1.3 and higher (.NET Core 1.0/1.1) and .NET Standard 2.0 and higher (.NET Core 2.0 and higher). It can be used with ASP.NET Core as well. Tested with .NET Core 1.0/1.1/2.0/2.1/2.2/3.0/3.1 and .NET 5.0/6.0/7.0/8.0/9.0/10.0.

.NET Core 1.0/1.1

.NET Core 1.0/1.1 (.NET Standard 1.3) edition mostly has .NET 4.5 feature set (including async/await methods) with the following limitations:

License key can only be set in the code (no Windows Registry, machine.config and so on).
No sync versions of many methods, only async/await versions. You may get PlatformNotSupportedException when calling, let's say, Imap.Connect instead of Imap.ConnectAsync (this seems to be an issue with .NET Core 1.0/1.1 only).
BounceMail requires .NET Standard 2.0 edition at least.
ICalVCard library is not compatible with .NET Core.
Mail merge and e-mail address validation over database requires .NET Standard 2.0 edition at least.
No RTF-to-HTML conversion during parsing MS-TNEF (winmail.dat), Outlook .MSG and .PST files.
No HTML to PDF conversion (MailBee.Pdf component is not supported).
No EWS (Exchange Web Services) support.
S/MIME can only work on Windows.
Direct send without SMTP relay server: no system DNS server autodetection via WMI, config file or Windows Registry. It still works on Windows but may not work on other platforms. The affected method: DnsServerCollection.Autodetect. You can still add DNS servers manually, e.g. by filling Global.DnsServers collection.

.NET Core 2.0 and newer

.NET Core 2.0 (.NET Standard 2.0) edition has much fewer limitations:

No HTML-to-PDF conversion.
ICalVCard library not supported (you can use other open-source alternatives like iCal.NET).
No impersonation (doesn't make sense in .NET Core anyway).
Limited support of certificate stores (no Win32-specific functions).

What you need to run MailBee with .NET Core

The MailBee.NET.dll for .NET Core resides in C:\Program Files (x86)\MailBee.NET Objects\.netstandard1.3 folder (...\.netstandard2.0 for .NET Core 2.0 and newer). Or, via NuGet, the required .DLL will be installed automatically. Just run this command:

Install-Package MailBee.NET

Install System.Text.Encoding.CodePages package (for .NET Core 2.0+):

Install-Package System.Text.Encoding.CodePages

Encoding.RegisterProvider(CodePagesEncodingProvider.Instance) must be called before accessing any MailBee classes. This initializes codepages support in .NET Core runtime.

Filesystem access (paths to locations accessible for reading or writing files) is also platform-specific and can depend on your application settings and permissions. If you just need some place where to save the log file for debugging, System.Environment.GetFolderPath(System.Environment.SpecialFolder.MyDocuments) folder can be used.

Send feedback to AfterLogic