go-azure-functions VS azure-functions-dotnet-worker

💡 You can clone the repo I have created from here.

The official example also doesn't use that. https://github.com/Azure/azure-functions-dotnet-worker/blob/main/samples/FunctionApp/Program.cs

Found that newer versions of the function runtime is completely broken (Incidentally i need to use durable functions, so this is annoying on multiple levels). https://github.com/Azure/azure-functions-dotnet-worker/issues/556

The Azure Functions .NET worker has been out for a while, and it finally enabled developers to use C# 9 and .NET 5 on function apps. This is a new way to create C# function apps, it now has a Program.cs class, with the good old generic Host builder and all the extension methods that we're used to see on regular ASP.NET Core and Worker service projects. This is how it can look:

name: Build & Deploy on: push: branches: - master pull_request: env: FUNCTION_PACKAGE_PATH: .publish/function RESOURCE_GROUP: az-function-fsharp-net5 jobs: build-and-deploy: runs-on: ubuntu-18.04 steps: - name: Checkout code uses: actions/checkout@master with: fetch-depth: 0 - name: Setup dotnet SDK 3.1 (https://github.com/Azure/azure-functions-dotnet-worker/issues/480) uses: actions/setup-dotnet@v1 with: dotnet-version: "3.1.409" - name: Setup dotnet SDK uses: actions/setup-dotnet@v1 with: dotnet-version: "5.0.300" - name: Publish Function run: dotnet build src/Function -c Release -o ${{ env.FUNCTION_PACKAGE_PATH }} - name: Login to Azure uses: azure/login@v1 with: creds: ${{ secrets.AZURE_RBAC_CREDENTIALS }} - name: Deploy to Azure uses: azure/CLI@v1 with: inlineScript: ./deploy.sh ${{ env.FUNCTION_PACKAGE_PATH }} -g ${{ env.RESOURCE_GROUP }}

There is a GitHub issue for this as well. https://github.com/Azure/azure-functions-dotnet-worker/issues/283

But how does this work? The idea is pretty straight forward, you create a class with properties for all the output values and decorate them with output binding attributes. Here is an example borrowed from the official Samples.

The biggest change is the way output bindings are changed and not clear from the example above, if you want to use multiple outputs you need to define them in a class and use it a a return type. This is illustrated in the example below that I have borrowed from the official repository.