You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of .NET does your existing project use?
.NET 6
What version of .NET are you attempting to target?
.NET 8
Description
I followed instructions to migrate my function app from .NET6 to .NET8 by setting <TargetFramework>net8.0</TargetFramework> <AzureFunctionsVersion>v4</AzureFunctionsVersion>
upgraded to <PackageReference Include="Microsoft.NET.Sdk.Functions" Version="4.5.0" />
in my csproj file.
In my local.settings.json file I included these three settings: "FUNCTIONS_WORKER_RUNTIME": "dotnet", "FUNCTIONS_EXTENSION_VERSION": "~4", "FUNCTIONS_INPROC_NET8_ENABLED": "1",
When I build my solution however, I am getting the above error: Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Microsoft.AspNetCore.Mvc.Core, Version=8.0.0.0
Project configuration and dependencies
Link to a repository that reproduces the issue
No response
The text was updated successfully, but these errors were encountered:
What version of .NET does your existing project use?
.NET 6
What version of .NET are you attempting to target?
.NET 8
Description
I followed instructions to migrate my function app from .NET6 to .NET8 by setting
<TargetFramework>net8.0</TargetFramework>
<AzureFunctionsVersion>v4</AzureFunctionsVersion>
upgraded to
<PackageReference Include="Microsoft.NET.Sdk.Functions" Version="4.5.0" />
in my csproj file.
In my local.settings.json file I included these three settings:
"FUNCTIONS_WORKER_RUNTIME": "dotnet",
"FUNCTIONS_EXTENSION_VERSION": "~4",
"FUNCTIONS_INPROC_NET8_ENABLED": "1",
When I build my solution however, I am getting the above error: Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Microsoft.AspNetCore.Mvc.Core, Version=8.0.0.0
Project configuration and dependencies
Link to a repository that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: