-
Notifications
You must be signed in to change notification settings - Fork 66
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
Using Microsoft.WindowsAzure.Storage (WindowsAzure.Storage) 9.1.1 in a Function is failing on call to Newtonsoft outside of its dependency #194
Comments
I am facing the same issue. A PR was submitted: #200 but is not yet pushed to nuget. |
Any news on when this will be released please? |
I'm getting the same error, any news about this? Downgrading WindowsAzure.Storage to 8.7.0 makes it workable again. |
That PR is closed instead of merged. V1 function locks Newtonsoft.Json to 9.0.1 and it won't be changed, see the explanation. |
Related to this issue? #266 |
Closing. Please see explanation. |
…on package which occurred preventing the running of the azure functions. This is a recommended workaround as per: Azure/azure-functions-vs-build-sdk#194
InnerException {"Could not load file or assembly 'Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.":"Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed"} System.Exception {System.IO.FileNotFoundException}
Why is the it looking for 10.0.0.0 when it has a dependency on Newtonsoft >= 10.0.2
I have tried with various versions of WindowsAzure.Storage and it only works within the Function when using version 8.7.0 which has a dependency on Newtonsoft >= 6.0.8
Another user can reproduce and suggests this is a bug.
It seems the Function App SDK has a dependency related issue. The issue that it seems not related to WindowsAzure.Storage 9.1.1 itself. As WindowsAzure.Storage 9.1.1 and Newtonsoft 11.0.2 are working correctly in the console application.
More information about the bug detailed here: https://stackoverflow.com/questions/49812091/microsoft-windowsazure-storage-windowsazure-storage-9-1-1-failing-on-call-to-n
The text was updated successfully, but these errors were encountered: