-
Notifications
You must be signed in to change notification settings - Fork 69
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
Version 1.15.1 and 1.15.2 - Could not load file or assembly Microsoft.Extensions.Options #292
Comments
Hi @coder-candace Could you please let me know what is the target framework set for your library |
Hi @epasos573 yes the target framework is .NET Core 3.1. I was able to further narrow down where the problem is occurring. It's happening on this line. If you remove that line, error goes away and project fires up as expected. Add it back and error returns. Problem is if we just remove this line then our Configure() override won't run and we can't set up required application settings. Here is a sample project demonstrating the issue |
Hi @coder-candace Thanks for the sample code and after verifying the issue, I could see that the To replicate the issue, I have updated the sample code you have provided. I uninstalled Testing the case further, I have used the
See attached updated project |
I also have the same issue - basic install into a .NET Core 3.1 DLL with only these dependencies.
|
@JT-Bruch The CloudinaryDotNet SDK is compatible with As for your case, reviewing the dependencies requirements for Please take a look and see if that helps. |
Could not load file or assembly 'Microsoft.Extensions.Options, Version=5.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.
We are using the SDK in a .NET Core 3.1 Azure Function project. On startup we get the following error message.
In order to resolve the error we have to downgrade to version 1.14.0.
…
Issue Type (Can be multiple)
Steps to reproduce
Simply upgrade the NuGet package and try to run the project. Error will occur during startup.
Error screenshots or Stack Trace (if applicable)
OS and Version
Versions and Libraries (fill in the version numbers)
The text was updated successfully, but these errors were encountered: