Cross.Messaging 2.3.0

.NET 6.0 This package targets .NET 6.0. The package is compatible with this framework or higher. .NET Standard 2.1 This package targets .NET Standard 2.1. The package is compatible with this framework or higher. 
dotnet add package Cross.Messaging --version 2.3.0
                    


                    

                
NuGet\Install-Package Cross.Messaging -Version 2.3.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Cross.Messaging" Version="2.3.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Cross.Messaging" Version="2.3.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Cross.Messaging" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add Cross.Messaging --version 2.3.0
                    


                    

                
#r "nuget: Cross.Messaging, 2.3.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package Cross.Messaging@2.3.0
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=Cross.Messaging&version=2.3.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Cross.Messaging&version=2.3.0
                    


                            Install as a Cake Tool

License GitHub Release Date NuGetVersion NugetDownloads Coverage issues .NET PR

Size GitHub contributors GitHub commits since latest release (by date) Activity Activity Activity

Cross.Messaging

A set of libraries for sending messages across multiple channels.

Current focus:

  • Email (Cross.Messaging.Email.*)
  • SMS (Cross.Messaging.Sms.*)
  • Telegram (Cross.Messaging.Telegram.*)
  • Viber (Cross.Messaging.Viber.*)
  • WatsApp (Cross.Messaging.WatsApp.*)

Supported targets: .NET Standard 2.1, .NET 6, .NET 7, .NET 8, .NET 9, .NET 10

Install NuGet package

Install the Cross.Messaging NuGet package into your .NET project:

Install-Package Cross.Messaging

or

dotnet add package Cross.Messaging

Quick start

Register the email sender in DI

services.AddEmailSender(configuration);

AddEmailSender:

  • binds the MessagingEmail configuration section to MessagingEmailOptions
  • registers IEmailSenderService → EmailSenderService (scoped)

Email sender API

IEmailSenderService currently exposes:

  • SendAsync(toName, toEmail, subject, body, cancellationToken)
  • SendAsync(toName, toEmail, subject, body, priority, cancellationToken)
  • SendAsync(toName, toEmail, subject, textBody, htmlBody, cancellationToken)
  • SendAsync(toName, toEmail, subject, textBody, htmlBody, priority, cancellationToken)
  • SendAsync(toName, toEmail, subject, textBody, htmlBody, attachments, cancellationToken)
  • SendAsync(toName, toEmail, subject, textBody, htmlBody, priority, attachments, cancellationToken)
  • SendAsyncWithContentIds(toName, toEmail, subject, textBody, htmlBody, attachments, contentIdMap, cancellationToken)
  • SendAsyncWithContentIds(toName, toEmail, subject, textBody, htmlBody, priority, attachments, contentIdMap, cancellationToken)

If you use attachment overloads, pass IReadOnlyCollection<IFormFile>? (Microsoft.AspNetCore.Http).

Example:

await emailSender.SendAsync(
    toName: "User",
    toEmail: "user@example.com",
    subject: "Hello",
    textBody: "Plain text body",
    htmlBody: "<p>HTML body</p>",
    priority: XMessagePriority.Normal,
    attachments: null,
    cancellationToken: cancellationToken);

Sample email configuration

{
  "MessagingEmail": {
    "SmtpHost": "smtp.example.com",
    "SmtpPort": 587,
    "UseSsl": true,
    "SecureSocket": "StartTls",
    "SmtpLogin": "login",
    "SmtpPassword": "password",
    "FromUserName": "App Messaging",
    "FromUserAddress": "no-reply@example.com",
    "RecipientOverride": "",
    "BccRecipients": [
      {
        "Name": "Audit Bot",
        "Email": "audit@example.com"
      }
    ]
  }
}

BccRecipients is optional; when configured, each entry is added to outgoing messages as BCC.

Entries with empty Email are ignored.

Register the SMS sender in DI

services.AddSmsSender(configuration);

AddSmsSender:

  • binds the MessagingSms configuration section to MessagingSmsOptions
  • registers ISmsSenderService → SmsSenderService (scoped)
  • registers an SMS provider only when it is referenced by DefaultProvider or CountryProviders and also has settings under MessagingSms:Providers (evaluated at startup; restart if a reload references a provider that was not registered then)

ISmsSenderService.SendAsync(destination, body, cancellationToken) expects destination in E.164 (+...). The country is resolved from the calling code (longest-prefix match); NANP +1 maps to US.

DefaultProvider is used for all destinations unless the resolved country has an override in CountryProviders (list only exceptions there, not every country).

Sample SMS configuration

{
  "MessagingSms": {
    "DefaultProvider": "Telnyx",
    "CountryProviders": {
      "RO": "SMSClub"
    },
    "Providers": {
      "Telnyx": {
        "ApiKey": "KEY",
        "From": "+15551234567",
        "MessagingProfileId": ""
      },
      "SMSClub": {
        "ApiKey": "TOKEN",
        "From": "MySender"
      }
    }
  }
}

MessagingProfileId is optional and used for Telnyx modes that require a messaging profile (for example number pool / alphanumeric sender).

For SMSClub, ApiKey is the Bearer token and From is the alphanumeric sender name (src_addr).

Unit tests

Tests use the Given_When_Then naming style:

  • Given — context and preconditions.
  • When — the action under test.
  • Then — the expected outcome.

Example: Given_ValidSmtpOptions_When_SendAsync_Then_UsesConfiguredHost.

Tests live in Cross.Messaging.Tests/ (for example Email/, Sms/).

Available NUnit categories:

  • Unit
  • Integration

Run only unit tests (NUnit Category=Unit):

dotnet test Cross.Messaging.Tests/Cross.Messaging.Tests.csproj --filter "Category=Unit"

Run only integration tests (NUnit Category=Integration):

dotnet test Cross.Messaging.Tests/Cross.Messaging.Tests.csproj --filter "Category=Integration"

Code coverage

Run tests with code coverage (opencover):

dotnet test Cross.Messaging.Tests/Cross.Messaging.Tests.csproj \
 --collect:"XPlat Code Coverage" \
 --results-directory ./TestResults \
 -- DataCollectionRunSettings.DataCollectors.DataCollector.Configuration.Format=opencover
Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
.NET Core netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.1 is compatible. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on Cross.Messaging:

Package Downloads
Cross.Identity

Identity and authentication library for .NET: configurable flows (registration, login, forgot password, token, refresh), JWT, Argon2, email/SMS verification, process engine with JSON-defined flows. External OAuth.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.3.0 59 11/4/2026
2.3.0-preview.2 45 11/4/2026
2.3.0-preview.1 48 11/4/2026
2.2.0 75 11/4/2026
2.2.0-preview.7 38 11/3/2026
2.2.0-preview.6 34 11/3/2026
2.2.0-preview.5 36 11/3/2026
2.2.0-preview.3 43 11/3/2026
2.1.0 1,731 5/8/2026
2.1.0-preview.1 107 5/8/2026
2.0.0 152 5/5/2026
2.0.0-preview.9 77 5/5/2026
1.2.0-preview.10 82 5/5/2026
1.2.0-preview.9 89 5/5/2026
1.2.0-preview.6 85 5/5/2026
1.1.4 172 4/26/2026
1.1.2 183 4/17/2026
1.1.1 213 4/10/2026
Loading failed

- SMS: added Telnyx and SMSClub providers, country→provider routing from E.164 (e.g. RO→SMSClub), MessagingSms options, and AddSmsSender DI extension.
- Email: added configurable `BccRecipients` in `MessagingEmail` section (`Name`, `Email`) for send flows.
- Email API: added priority overloads for `SendAsync(...)` and `SendAsyncWithContentIds(...)`, plus `SendAsync(...)` overloads without attachments.
- Tests: added category tags (`Unit`, `Integration`) and expanded service tests for new overloads.
- Documentation: updated README examples for API, categories, and category-based test execution.