Skip to content
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 .14 fails to load Newtonsoft.Json Version=11 out of the box #218

Closed
LeviSchuck opened this issue Aug 12, 2018 · 2 comments
Closed
Labels

Comments

@LeviSchuck
Copy link

My azure function fails at runtime with the following message

Executed 'HttpTrigger' (Failed, Id=d431dc42-3683-407f-9738-7e4b501547b7)
System.Private.CoreLib: Exception while executing function: HttpTrigger.<ProjectName>: Could not load file or assembly 'Newtonsoft.Json, Version=11.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'. Could not find or load a specific file. (Exception from HRESULT: 0x80131621). System.Private.CoreLib: Could not load file or assembly 'Newtonsoft.Json, Version=11.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'.

Reproduced by

  1. Create a new project for an azure function
  2. Under dependencies, update Microsoft.NET.Sdk.Functions from 1.0.13 to 1.0.14
  3. Press play and curl to the HttpTrigger

Observe that without updating the dependency from 1.0.13 (which uses an old Newtonsoft.Json), it works fine--although this dependency blocks many useful libraries due to incompatibility.

I have also added <PackageReference Include="Newtonsoft.Json" Version="11.0.2" /> and this does not resolve this problem.

Here is a 2 minute recording demonstrating a new project from scratch, which uses 1.0.13 (and works), and then does not work after merely updating.
https://youtu.be/v4DuNIA8dG4

@LeviSchuck
Copy link
Author

Secondly, remaining on 1.0.13 and adding <PackageReference Include="Newtonsoft.Json" Version="11.0.2" /> reproduces the same problem.

@vijayrkn
Copy link
Collaborator

vijayrkn commented Feb 4, 2019

This should be fixed with the GA version Please update to the latest and re-open the issue if you run into this issue again.

@vijayrkn vijayrkn closed this as completed Feb 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants