Azure / Azure/azure-functions-openapi-extension
TypeLoadException on .NET 10 with Azure Functions OpenAPI Extension
- Dominant language
- C#
- Stars
- 388
- Forks
- 202
- PR merge metrics
- No merged PRs in 30d
Description
After upgrading our Azure Functions project to .NET 10 (isolated worker), the OpenAPI extension fails to start. The app runs fine on .NET 8 with the same package versions.
Error
System.TypeLoadException:
Method 'GetOpenApiFormat' in type
'Microsoft.Azure.Functions.Worker.Extensions.OpenApi.OpenApiHttpTriggerContext'
does not have an implementation
Environment
Microsoft.Azure.Functions.Worker.Extensions.OpenApi v1.6.0
Microsoft.Azure.Functions.Worker v2.0.0
TargetFramework: net10.0
Isolated worker process
Reproduction Steps
Create a .NET 10 Azure Functions app (isolated worker).
Install the OpenAPI extension NuGet package.
Run the function — fails with the above TypeLoadException.
Additional Notes
Downgrading to .NET 8 works fine with the same package versions.
We are looking for guidance on whether .NET 10 is officially supported, or any workarounds to make it work.
Question
Is there a stable version of the OpenAPI extension planned for .NET 10?
Are there any recommended workarounds to avoid this startup failure?
Contributor guide
Research direction
Start by reproducing the startup failure in a .NET 10 isolated-worker app with Microsoft.Azure.Functions.Worker.Extensions.OpenApi v1.6.0 and Microsoft.Azure.Functions.Worker v2.0.0, then compare it with the reported .NET 8 behavior. Trace the OpenAPI extension entry point and the GetOpenApiFormat TypeLoadException; done means establishing .NET 10 support status and documenting a verified workaround or compatibility fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, openapi
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100