-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While upgrading .net project from 6 to 8, got error #110405
Comments
Tagging subscribers to this area: @dotnet/area-meta |
Tagging subscribers to this area: @dotnet/area-extensions-configuration |
Please try to provide a sample project demonstrating the issue so we can help tell you what exactly the problem is. My guess here is your project is referencing some other aspnet package with a different version than the one of the configurations abstraction version. |
This issue has been marked |
CC @ericstj |
Seems like this is coming from Azure Functions: https://github.com/Azure/azure-functions-host/blob/255b7e59538b9ab677d653daf347b3b0afa70dc9/src/WebJobs.Script/ScriptHostBuilderExtensions.cs#L280 As @tarekgh suggests there is some component that isn't updating. I know Azure Functions control some of the versions of these assemblies when using the "in-process" model, so it could be that you're compiling against one thing but running against a different thing. You might find the following resource helpful: cc @fabiocav |
This issue has been automatically marked |
This issue will now be closed since it had been marked |
This issue has been moved from a ticket on Developer Community.
While upgrading .net project from 6 to 8, I got error says: could not load file or assembly 'Microsoft.Extensions.Configuration.Abstractions, Version=8.0.0.0.
Steps I performed to troubleshoot are:
Error message
Original Comments
Feedback Bot on 11/27/2024, 09:32 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
The text was updated successfully, but these errors were encountered: