NServiceBus 7.8

Last reviewed Sep 20, 2026

Export as PDF

Prompt Details

Prompt Composition

2prompts
  1. C# 14106 lines · 4.4K tokens
  2. NServiceBus 7.8112 lines · 5.2K tokens
Total218 lines · 9.6K tokens

CWE Coverage

  • 20
  • 22
  • 59
  • 78
  • 89
  • 94
  • 117
  • 190
  • 208
  • 209
  • 214
  • 250
  • 257
  • 295
  • 306
  • 319
  • 323
  • 327
  • 338
  • 345
  • 362
  • 367
  • 378
  • 426
  • 502
  • 532
  • 611
  • 636
  • 639
  • 674
  • 759
  • 770
  • 772
  • 775
  • 778
  • 798
  • 807
  • 829
  • 841
  • 862
  • 863
  • 915
  • 916
  • 918
  • 922
  • 1333
  • 1395

Prompt Preview

Apply the C# 14 prompt first when using that language version. These rules cover NServiceBus 7.8, including its default XML message serializer and BinaryFormatter-based DataBus default. The package targets .NET Standard 2.0 and .NET Framework 4.5.2; NServiceBus 7 does not require C# 14.

Legacy support and migration

  • Lock the NServiceBus dependency to the newest 7.8 patch available to you through Central Package Management or a lock file, and select compatible, supported transport, persistence, serializer, DataBus, hosting, and monitoring packages; support requires the latest patch of the applicable supported minor line.
  • Treat this as a short-lived migration target: mainstream support ended 2024-11-17 and paid extended support ends 2026-11-17, after which public fixes are not promised.
  • Confirm a valid Particular extended-support agreement for any production dependency on 7.8; critical patches during extended support are supplied only to eligible customers.
  • Treat .NET Core 2.0 and .NET Framework 4.5.2 as historical compatibility minimums, not supported deployment targets; use a patched Microsoft-supported runtime and Windows or Linux platform supported by the selected components. Particular supports macOS for development only.
  • Audit the resolved dependency graph as well as the core package. The .NET Standard asset declares System.Security.Cryptography.Xml 4.7.1 as its minimum, and a plain restore stops at that old package line, which the 2026 System.Security.Cryptography.Xml advisories neither list as affected nor patch, so NuGet audit has nothing to