Caution
NServiceBus.AzureFunctions.InProcess.ServiceBus has been officially sunsetted.
Microsoft announced that .NET 8 will be the last release supporting the in-process hosting model.
We will continue to provide support and address critical fixes during the sunset period, but no new features will be added.
New projects should use the isolated worker model instead, see migration instructions below.
NServiceBus.AzureFunctions.InProcess.ServiceBus supports processing messages in Azure Functions using the Azure Service Bus trigger and the NServiceBus message pipeline.
It is part of the Particular Service Platform, which includes NServiceBus and tools to build, monitor, and debug distributed systems.
To prepare for migration, please review:
- Migration instructions from InProcess to the Isolated model.
- Migration instructions from the old isolated package to the new multi-endpoint isolated package.
Review both migration guides and decide whether the safer approach is to first migrate from InProcess to the isolated package and then upgrade to the latest multi-endpoint package, or whether a direct migration from InProcess to the latest multi-endpoint package is acceptable.
See the Azure Functions with Azure Service Bus (in-process) documentation for more details on how to use it.
Requirements:
- Have the Microsoft Azurite Storage Emulator running
- Configure an environment variable named
AzureWebJobsServiceBuswith an Azure Service Bus connection string