0

We want to upgrade an existing In-Process Azure Function to .NET 7.0, since we want to migrate the dependencies to .NET 7.0 too. This Azure Function uses the ServiceBusReceivedMessage and its metadata, which does not seem to be supported in Isolated Azure Functions.

Creating a wrapper JSON object which contains the metadata of the message is not an option just in order to upgrade to .NET 7.0 (then we would rather stay .NET 6.0 for now).

Do we have to wait for Microsoft to either support ServiceBusReceivedMessage in isolated Azure Function or support .NET 7.0 for in-process Azure Functions, or do I miss something?

It is a bit sad that only due to the fact that we have an Azure Function we cannot upgrade our entire solution to .NET 7.0.

Fabian Bigler
  • 10,403
  • 6
  • 47
  • 70

1 Answers1

1
  • AFAIK, We have to wait for update of ServiceBusReceivedMessage in .NET 7 both in-process and Isolated Worker process.
  • Because ServiceBusReceivedMessage is part of Azure.Messaging.ServiceBus Package that is available up to .NET 6 In-Process Version as shown here.

https://i.stack.imgur.com/7AOVU.png

  • Here is an SO Thread that show how to use the Service Bus Message Class in .NET 6 Isolated Azure Functions.
  • As .NET 7 Isolated Process came recently (Nov 1st Week) - to know the update of ServiceBusReceivedMessage in .NET 7, please raise the ticket in Azure-sdk-for-net GitHub Repository.
Pravallika KV
  • 2,415
  • 2
  • 2
  • 7