WorkerConfig for runtime: dotnet-isolated not found

Question

Created a .NET 6.0 Isolated Function (with HTTP Trigger) in Visual Studio 2022. But when running/debug this function locally, get following error:

Microsoft.Azure.WebJobs.Script: WorkerConfig for runtime: dotnet-isolated not found. Value cannot be null. (Parameter 'provider')

Error details from console:

Local.settings.json:

{
    "IsEncrypted": false,
  "Values": {
    "AzureWebJobsStorage": "UseDevelopmentStorage=true",
    "FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated"
  }
}

host.json:

{
  "version": "2.0",
  "logging": {
    "applicationInsights": {
      "samplingSettings": {
        "isEnabled": true,
        "excludedTypes": "Request"
      }
    }
  }
}

.csproj file:


  
    net6.0
    v4
    Exe
    enable
    enable    
  
  
    
    
    
    
  
  
    
      PreserveNewest
    
    
      PreserveNewest
      Never

Program.cs

using Microsoft.Extensions.Hosting;

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

host.Run();

Project can be found in this GitHub Repo: FunctionAppTest

user_15969981 · Answer

One of the workarounds is to add program.cs in your application and adding following references in your .csproj.

Make sure before you run the application try deleting the contents of your bin, Clean and Build your solution.

Try checking this similar thread.

user_1706008 · Answer

I had experienced the same error message:

Microsoft.Azure.WebJobs.Script: WorkerConfig for runtime: dotnet-isolated not found.

This also occurred when deployed to Azure (in a Consumption Plan, but it seemed to be a general issue on Azure hosting).

The resolution for me was to update the nuget package related to the worker process, specifically Microsoft.Azure.Functions.Worker. The project created from the Functions template originally had a reference to version 1.6.0, and this exhibited the above error; upgrading to the latest, which as of the time of posting, is version 1.8.0, resolved all issues.

Both local debugging and publishing to Azure was successful, and the Function behaved as expected.

user_11706223 · Answer

I had this issue when deployed to the azure, i had to remove this package to resolve the issue.

please try removing the package - Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator

Microsoft.Azure.WebJobs.Script: WorkerConfig for runtime: dotnet-isolated not found

WorkerConfig for runtime: dotnet-isolated not found

3 Answers