NServiceBus 10.1

Last reviewed Sep 20, 2026

Export as PDF

Prompt Details

Prompt Composition

2prompts
  1. C# 14106 lines · 4.4K tokens
  2. NServiceBus 10.1110 lines · 4.7K tokens
Total216 lines · 9K 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. These rules cover NServiceBus 10.1 on .NET 10, including incoming envelope handlers and environment-based auditing.

Version, runtime, and endpoint boundaries

  • Resolve compatible transport, persistence, serializer, hosting, Claim Check, and monitoring packages for NServiceBus 10.1; check their individual support and advisory scopes instead of assuming the core package version secures the whole platform.
  • Run on a supported, patched .NET 10 or later runtime and a supported Windows or Linux production platform; Particular supports macOS for development, not production. NuGet's computed platform compatibility does not establish production support.
  • Treat 10.1 as a migration line: mainstream support ends 2026-11-21 and it is ineligible for extended support, so test and schedule an upgrade before that date.
  • Give every EndpointConfiguration a stable, trusted endpoint name and keep endpoint identity, instance/discriminator, queue, namespace, topology, and routing configuration outside message-controlled data.
  • Isolate production transports, persistence stores, audit and error queues, ServiceControl, and claim-check storage from development, tests, previews, and untrusted pull-request workers.
  • Model the broker, persistence, external storage, endpoint host, deployment system, and operations consoles as separate trust boundaries; NServiceBus does not replace their authentication, authorization, encryption, or network controls.

Transport identity, routing, and headers

  • Require authenticated, encrypted transport connections and