Universal Messaging 10.1 | Developer Guide | Enterprise APIs | Enterprise Developer's Guide for C# | Prerequisites | Using UM API libraries for .NET in .NET Standard projects
Using UM API libraries for .NET in .NET Standard projects
The Universal Messaging API for .NET is built and tested against .NET Framework 4.5, which implements .NET Standard 1.1. However it is verified that the Nirvana DotNet.dll, Nirvana nAdminAPI.dll and Nirvana.Reactive.dll APIs are compatible with .NET Standard 2.0. This means that they can be used in .NET Standard 2.0+ compatible runtimes, such as .NET Core 2.0. For the verification, the ".NET Portability Analyzer" tool is used ( https://docs.microsoft.com/en-us/dotnet/standard/analyzers/portability-analyzer).
The SASL authentication available with the Universal Messaging API for .NET cannot be used in a .NET Standard 2 project. SASL is implicitly used when a password is passed on session creation using the nSessionFactory.create(..., NetworkCredential creds) API.
An exception such as the following will be thrown on session init in this case:
Message=Realm is currently not reachable:
Requested SASL mechanisms not supported by chosen library.