No job functions found, migrating to .net 8 isolated worker process – Azure

The Problem:

Migrating Azure Functions app to run in an isolated worker process in .Net 8, but no job functions are found during runtime. The console displays messages like ‘No job functions found. Try making your job classes and methods public.’ and ‘0 functions found’ while reading functions metadata.

The Solutions:

Solution 1: Configure the project correctly

To migrate an Azure Function app to run in an isolated worker process in .NET 8, you need to configure your project correctly. This includes:

1. Installing .NET 8.0 and the latest Azure Function core tools

2. Updating your project’s .csproj file to target .NET 8.0 and specify the Azure Functions Version as v4

3. Adding the necessary NuGet packages, including Microsoft.Azure.Functions.Worker and Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore

4. Adding the required configuration to your local.settings.json file, including setting the FUNCTIONS_WORKER_RUNTIME to dotnet-isolated

5. Updating your Program.cs file to configure the Functions host to use the isolated worker process model.

using Microsoft.Azure.Functions.Worker;

var host = new HostBuilder()
    .ConfigureFunctionsWorkerDefaults()
    .Build();

await host.RunAsync();

6. Creating your function classes and methods in a public class

7. Running the function app locally using the Azure Functions Core Tools

8. Deploying the function app to Azure

Once you have completed these steps, your Azure Function app should be running in an isolated worker process in .NET 8.

\n

Solution 2: Update Azure Portal Configuration using Bicep Template

\n

To migrate your Azure Functions app to .NET 8 isolated worker process, you need to update the configuration in the Azure Portal using a Bicep template. Here’s how you can do it:

1. Add the following properties to your Bicep template under the siteConfig object within the functionApp resource:

use32BitWorkerProcess: false
netFrameworkVersion: 'v8.0'

2. Ensure that you are using the correct value for functionRuntime. For .NET 8 isolated worker process, the supported value is dotnet-isolated.

By making these changes, you are explicitly specifying that you want to use the .NET 8 isolated worker process and 64-bit platform for your Azure Functions app. This should resolve the issue of not finding any job functions when running your application in .NET 8.

Note:

• Make sure to replace functionAppName, appInternalServiceName, keyVault, storageAccount, appInsightsInstrumentationKey, functionRuntime, and appTags with the actual values for your Azure Functions app.
• You can find more information about Bicep templates for Azure Functions in the official documentation.

Video Explanation: