Could not load file or assembly 'Newtonsoft.Json, Version=4.5.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'

Question

I am getting the Error

System.IO.FileLoadException : Could not load file or assembly 'Newtonsoft.Json, Version=4.5.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

for my CI build

Solution which I tried

<dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed"
        culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
</dependentAssembly>

It also did not work

The error means .NET couldn't find the [Json.NET](http://json.codeplex.com/) library. [Do you have it installed?](http://stackoverflow.com/questions/6176841/could-not-load-file-or-assembly-newtonsoft-json-version-3-5-0-0?rq=1) — TypeIA, Mar 19 '14 at 13:24
Exact same problenm - driving me nuts. Let me know if you find a solution — Dean Chalk, Apr 01 '14 at 18:11
Use the consolidate option in NuGet package manager to ensure versions don't drift apart. — niico, Apr 12 '17 at 09:08
This is the only thing that worked for me: https://github.com/Redth/PushSharp/issues/361#issuecomment-181387928 — RichC, Dec 07 '18 at 19:00

score 257 · Answer 1 · edited May 19 '16 at 12:31

257

In package manager console execute: Update-Package –reinstall Newtonsoft.Json.

UPDATE

I originally posted this as a comment but as @OwenBlacker suggested I'll just put it here:

If you still get an error after doing this, then what worked for me eventually is that I deleted Json.Net's <dependentAssembly> section from my .config file. Reinstall brings it back if it's not there and apparently you need to delete it. Until there will be a normal solution in the package itself, I'm afraid this manual step is a must.

Note: Please read the comments below before doing this.

As per René's comment below BE AWARE that the command posted in the answer will reinstall the package in every project in your solution. So if you use the Newtonsoft.Json package in several projects and maybe use different versions, just executing the above command might have unwanted consequences.

edited May 19 '16 at 12:31

s_a

173
2
4

answered Apr 30 '14 at 07:00

bobah75

3,500
1
16
25

9

For the sake of everyone reading this: I've done that and still got the error. Then I solved it somehow: Amazingly, I had to _delete_ Json.Net's `` section from my `.config` file. Reinstall brings it back if it's not there and apparently you need to delete it. Until there will be a normal solution in the package itself, I'm afraid this manual step is a must. – Ofer Zelig Jun 27 '14 at 00:36
@OferZelig You should post that as a separate answer, so it can get the upvotes (and, more importantly, increased attention). Not least because it worked for me too :) – Owen Blacker Jul 03 '14 at 00:04
@OwenBlacker thanks. But because there are lots of answers already, mine will get lost. And this answer is quite good, it's just that if it doesn't work then my comment "completes" it. You know what? I guess I'll just edit the original answer. More important than gaining own rep. – Ofer Zelig Jul 04 '14 at 00:04
50

_BE AWARE_ that the command posted in the answer will reinstall the package in _every_ project in your solution. So if you use the Newtonsoft.Json package in several projects and maybe use different versions, just executing the above command might have unwanted consequences. – René Jul 10 '14 at 11:09
Solved! For me, I had v6 installed in one project, reinstalling from package manager brought it up to v7. – jv-dev Jul 20 '15 at 19:13
Had to do this to get [GeoIP2-dotnet](https://github.com/maxmind/GeoIP2-dotnet) up and running. – Matt Borja Nov 04 '15 at 23:44
i had the issue when i installed `Microsoft.Owin.Security.Facebook` then automatically `Newtonsoft.Json` was installed and version changed from 4.5.0.0 to 6.0.0.0 and then [this](http://westdiscgolf.blogspot.com/2014/02/updated-jsonnet-and-now-owin-errors.html) post helped which similar to @ZeroDotNet answer to make changes in `web.config` ``, these recent update really effects the app, why they don't fix it – Shaiju T Dec 13 '15 at 11:53
Thanks this worked. I don't understand what happened. I updated my Json through NuGet and then suddenly this library is gone? – eaglei22 Dec 15 '15 at 14:41
The package manager command didn't work for me, but editing the app.config did. Thanks. – MonkeyWrench Jun 02 '16 at 18:44
package manager command worked like a charm for me, why isn't this the accepted answer? – Nebri Aug 14 '16 at 16:13
Old post but still having issues so recommend this: https://stackoverflow.com/a/38715898/12377 Worked for me. – Toby Mills Aug 05 '17 at 20:59
ahhh after hours wasted this fixed the package error. – revobtz Dec 07 '18 at 01:38

score 136 · Answer 2 · edited May 23 '17 at 12:26

136

To everyone having problems with Newtonsoft.Json v4.5 version try using this in web.config or app.config:

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
       <dependentAssembly>
           <assemblyIdentity name="Newtonsoft.Json"
               publicKeyToken="30AD4FE6B2A6AEED" culture="neutral"/>
           <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0"/>
       </dependentAssembly>
    </assemblyBinding>
</runtime>

IMPORTANT: Check that the configuration tag of your config file has no namespace attribute (as suggested in https://stackoverflow.com/a/12011221/150370). Otherwise, assemblyBinding tags will be ignored.

edited May 23 '17 at 12:26

Community

1
1

answered Jun 27 '14 at 21:32

ZeroDotNet

1,892
1
13
7

3

for me, deleting the content of the bin folder manually after cleaning (which does not empty it) did the trick after I applied this answer. – Mikaël Mayer Oct 02 '14 at 08:27
Works great! As of 7/4/15 the current version of Newtonsoft.Json is 7.0.0 so `newVersion="6.0.0.0"` must be changed to `newVersion="7.0.0.0"` or whatever version you are using – Moses Machua Jul 04 '15 at 04:26
I had a similar problem with DNN and the newtonsoft.json.dll, where DNN used version 4.5 and my module wanted to use 7.0. I didn't have access to upgrade the dnn installation with 7.0, so I added one of these dependentAssembly entries using oldversion= 0.0-7.0 and the 'new' version as the old 4.5. It worked. – Jake Gaston Aug 06 '15 at 17:44
For me the issue was that I had installed the latest version (8.*) but needed to downgrade to (6.*) because of other projects, the dependent assembly in the downgraded projects app.configs was still referencing 8.0.0.0 as the version, needed to change this to 6.0.0.0 – MaxJ Apr 21 '16 at 09:55
3

That note on the namespace...I could hug you. I burned hours on this not knowing the binding redirects were being ignored because of that. – Brian Nov 10 '16 at 14:55
1

The note about the namespace is so important that it could be an answer by its own. Thank you very much. – MÇT Nov 27 '19 at 07:47

Kadir Ercetin · Answer 3 · 2018-04-04T11:47:58.230

51

The key point is referencing right version in your config file.

Steps;

1- look at what is the version of your Newtonsoft.Json.dll in the project reference property what ever the version in your package folder (For example mine is 7.0.1 and the reference Version is 7.0.0.0)

2- look at what the project expect from you in the exception (mine is 6.0.0.0)

3- Add dependent assembly to your config file as it should be..

  <dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json"  publicKeyToken="30AD4FE6B2A6AEED" culture="neutral"/>
    <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="7.0.0.0"/>
  </dependentAssembly>

edited Apr 04 '18 at 11:47

answered Jul 14 '15 at 10:22

Kadir Ercetin

869
8
11

Sorry can give only one vote your point (For example mine is 7.0.1 and the referance Version is 7.0.0.0) made a huge difference. I would have given more.....Thanks :) – Zaker Dec 08 '15 at 07:43
This worked for me. I updated the version to 7, but it was really running version 8 so I just changed the newVersion to 8.0, thanks! – Keith Mar 09 '16 at 13:12
Even though installing 8.0.3 (like it says in nuget package manager), the .dll under references is still 8.0.0. So I changed to 8.0.0.0 in my web.config. Wierd how this worked yesterday when I published everything and this morning it does not work anymore. – CularBytes Apr 25 '16 at 07:39
How do you find the reference version? Using 12.0.3.0 in the redirect doesn't work but 12.0.0.0 does. Without pure fluke, how would I have worked that out? Is it detailed somewhere? It was unable to find 12.0.3.0 which exists in the bin folder, but it can find 12.0.0.0 apparently which literally doesn't exist as a versioned assembly ha! – Murphybro2 Mar 05 '21 at 14:29

score 26 · Answer 4 · edited Sep 20 '14 at 18:22

26

I had no luck with any of the solutions presented here (uninstalling, reinstalling, deleting references, creating bindingRedirects etc.) I had to go back to an old version of Newtonsoft. Version 5.0.6 had been working before, so I tried that one. I had to enter these two commands in the Package Console:

uninstall-package newtonsoft.json -force

install-package newtonsoft.json -version "5.0.6"

The -force option in the first command is required to force the uninstall. Dependencies with other assemblies prevent the uninstall without it.

edited Sep 20 '14 at 18:22

Lucas Zamboulis

2,494
5
24
27

answered Sep 20 '14 at 18:12

Karl Hoaglund

603
10
10

Worked like a charm. Had the error in my MVC 4 project. Almost switched to the native serializer. – Kees C. Bakker May 31 '15 at 19:41
thanks, I just needed to change -version "5.0.6" to -pre: install-package newtonsoft.json -pre – thiago.adriano26 Oct 24 '15 at 12:21

score 25 · Answer 5 · answered Nov 19 '14 at 16:26

25

I fixed the problem adding this binding redirect to my .config file:

<runtime>
    . . . 
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
            <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed"
                culture="neutral" />
            <bindingRedirect oldVersion="4.5.0.0" newVersion="6.0.0.0" />
        </dependentAssembly>
    </assemblyBinding>
</runtime>

The error message complains about not finding version 4.5.0.0, the current version of Newtonsoft.Json is 6.0.0.0 so the redirect should go from 4.5 to 6.0, not viceversa

answered Nov 19 '14 at 16:26

MiMo

11,793
1
33
48

Yes this solved my problem. So strange the amount of issues JSON.NET causes.. but once it goes its a dream machine. Thanks +1 – Piotr Kula Jul 21 '16 at 20:27
Your code snippet made me realize was missing 'assemblyBinding' element. Thanks – Ricardo stands with Ukraine Feb 22 '17 at 06:32

score 22 · Answer 6 · edited Jul 03 '14 at 00:04

22

I think you are pointing to the wrong target, change it to 4.5 instead of 6.0

<dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed"
        culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="4.5.0.0" />
</dependentAssembly>

This should work.

edited Jul 03 '14 at 00:04

Owen Blacker

4,117
2
33
70

answered Apr 10 '14 at 18:17

BrunoLM

97,872
84
296
452

1

Umbraco 7 required 4.5.0.0, so this helped get it up and running – MagicalArmchair Jan 13 '15 at 16:53

ekostadinov · Answer 7 · 2016-02-14T21:51:36.917

I've spend couple of days trying to resolve this frustrating issue. I've tried pretty much everything that can be found on the web. Finally I found that this error could be caused (like in my case) by the different target .Net project versions (4.5 and 4.5.1) in one solution. The steps bellow fixed it for me:

Double check the .Net version of every project that's in your solution. Just right click on project and go to Properties.

If possible set the same .Net version for all projects. If not at least try to change the Startup project one (for me this was the one causing the issues).
Remove all Newtonsoft.Json packs from the solution.

uninstall-package newtonsoft.json -force
Update all Newtonsoft.Json versions in all packages.config files, like so

<package id="Newtonsoft.Json" version="7.0.1" targetFramework="net451" />
Reinstall Newtonsoft.Json from "Package Manager Console" with:

install-package newtonsoft.json
Rebuild the solution

(Optional) 7. If you changed the Startup project, return it again

score 15 · Answer 8 · edited Jan 25 '16 at 03:16

15

uninstall-package newtonsoft.json -force
install-package newtonsoft.json

Did the trick for me :)

edited Jan 25 '16 at 03:16

Druid

6,423
4
41
56

answered Mar 27 '15 at 18:43

Chiranjeeb

211
2
5

1

this did the trick for me too. it automatically updated the webconfig file to the correct version. – Shaakir Jul 19 '16 at 09:48
Me too, this really helped. – Mike Malter Oct 17 '17 at 23:04
Other answers didn't work for me but this! It automatically updated both web.config and packages.config, thanks :) – jet_choong Nov 25 '21 at 12:52

score 13 · Answer 9 · answered Jun 25 '16 at 14:32

13

if you using multiple project in same solution and library of the one other check is all projects has same version of Newtonsoft.Json

answered Jun 25 '16 at 14:32

Fatih

945
15
26

This was my issue. Very frustrating going through all the responses above and getting no results. Finally figured it out when I bothered to check the version of the .dll in my Build folder. – Mar 22 '18 at 17:24

score 11 · Answer 10 · answered Mar 19 '14 at 13:25

11

Remove the Newtonsoft.Json assembly from the project reference and add it again. You probably deleted or replaced the dll by accident.

answered Mar 19 '14 at 13:25

helb

7,609
8
36
58

This approached works against a Xamarin Forms iOS project where I dropped the NuGet package and re-added it. Thanks. – The Senator Nov 30 '16 at 12:17

score 9 · Answer 11 · edited May 23 '17 at 12:03

9

I was writing a WebApi REST service client, so for me this error was caused by adding References to the System.Net.Http and System.Net.Http.Formatting assemblies manually via Add Reference, when I should have added the Microsoft.AspNet.WebApi.Client package via NuGet. See also this answer to another question.

edited May 23 '17 at 12:03

Community

1
1

answered Jun 24 '15 at 21:15

mschwaig

551
6
19

score 8 · Answer 12 · answered Mar 16 '17 at 11:24

You have 2 different versions of JSON.NET library in your solution. To solve this you should upgrade them to latest version. Follow these steps:

1-Open solution explorer 2-Right Click on solution name 3-Select Manage Nuget Packages for Solution 4-Select Updates from menu 5-Update JSON.NET package

This will resolve your issue.

link: Could not load file or assembly 'Newtonsoft.Json, Version=7.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies

The easiest and safest way to fix this problem. Thanks @mohammad — deanwilliammills, Jun 26 '18 at 13:32

Miguel Angelo · Answer 13 · 2014-03-19T13:37:12.087

Deploy the correct version to the CI machine

This is telling you that the assembly loader found a different version of the Newtonsoft.Json assembly, that does not match the reference you created in your project. To load the assembly correctly, you must either deploy the assembly side by side with your compiled code, or install the correct version of the assembly in the destination machine (i.e. in the GAC).

Alternative: make sure the configuration is in the correct file

If you want to keep the current solution, and load an assembly with a different version, make sure that the configuration you posted is in the correct .config file. Remember that there is no xpto.dll.config, a DLL loaded by an application always uses the config file of the running application.

score 6 · Answer 14 · answered Oct 03 '14 at 01:43

Normally adding the binding redirect should solve this problem, but it was not working for me. After a few hours of banging my head against the wall, I realized that there was an xmlns attribute causing problems in my web.config. After removing the xmlns attribute from the configuration node in Web.config, the binding redirects worked as expected.

http://www.davepaquette.com/archive/2014/10/02/could-not-load-file-or-assembly-newtonsoft-json-version4-5-0-0.aspx

score 5 · Answer 15 · edited Jan 25 '16 at 03:16

5

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json"
        publicKeyToken="30AD4FE6B2A6AEED" culture="neutral"/>
    <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="7.0.0.0"/>
  </dependentAssembly>
</assemblyBinding>

Works for me.... just put the version you are using in newVersion i.e(newVersion="7.0.0.0")

edited Jan 25 '16 at 03:16

Druid

6,423
4
41
56

answered Dec 27 '15 at 19:26

ali

51
1
1

Had this problem some times ago and this fixed in one hit. Thank you very much. – GutierrezDev Sep 14 '16 at 18:40

score 5 · Answer 16 · edited Feb 08 '22 at 07:04

5

Close solution.

Open packages.config and *.csproj with text editor and delete any line have Newtonsoft.Json

Ex:

<Reference Include="Newtonsoft.Json,Version=9.0.0.0,Culture=neutral,PublicKeyToken=30ad4fe6b2a6aeed, processorArchitecture=MSIL">
      <HintPath>..\packages\Newtonsoft.Json.9.0.1\lib\net40\Newtonsoft.Json.dll</HintPath>
      <Private>True</Private>
</Reference>

Or

<package id="Newtonsoft.Json" version="9.0.1" targetFramework="net40" />

Open solution again and re-install Newtonsoft.Json by Install-Package Newtonsoft.Json

It work for me.

edited Feb 08 '22 at 07:04

Bharat

2,441
3
24
36

answered Jul 02 '16 at 08:40

Trương Quốc Khánh

534
1
7
25

it works sometime but in the upcoming builds this problem came again n again – Heemanshu Bhalla Aug 12 '16 at 06:47
No problem if don't update it haha. Create trash project and install Newtonsoft.Json.dll, copy it (file dll) and add to your project reference. – Trương Quốc Khánh Sep 24 '16 at 06:51

score 5 · Answer 17 · edited Jan 04 '21 at 08:44

5

I was getting same error and by adding below code error resolved on production.

Answer is too late but might help someone.

    <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <dependentAssembly>
                <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-12.0.0.0" newVersion="12.0.0.0" />
            </dependentAssembly>
        </assemblyBinding>
    </runtime>

edited Jan 04 '21 at 08:44

Harun

667
7
13

answered Nov 28 '19 at 07:30

Bharat

2,441
3
24
36

Should add at the last line – Harun Jan 04 '21 at 05:05

score 4 · Answer 18 · answered Apr 14 '14 at 15:00

We had the exact same issue that you mentioned. We're using nunit to run tests through CI, and we have nunit running a file called tests.nunit, which describe a list of test dll fixtures to run.

Each test fixture had their own config file, but when run through the "tests.nunit" file the binding redirects seem to be ignored. The solution was to add the binding redirects to a new config file, "tests.config" that was beside the "tests.nunit" file.

score 4 · Answer 19 · edited Nov 04 '15 at 04:10

4

You should update the web.config file in the server. When nuget install NewtonSoft update this file including this code

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
  </dependentAssembly>
</assemblyBinding>

edited Nov 04 '15 at 04:10

answered Jun 11 '14 at 20:48

oaamados

666
10
17

In my case that was exactly my solution, put into app.config. "Assembly versions can be redirected in application, publisher policy, or machine configuration files." – datps Aug 02 '16 at 06:01

score 4 · Answer 20 · answered Mar 04 '15 at 13:29

I have got the same type of problem. And I also solved it just doing the following: Go to TOOLS > NuGet Package Manager and Select Package Manager Console. Finally, execute the following two commands :)

uninstall-package newtonsoft.json -force
install-package newtonsoft.json

score 4 · Answer 21 · answered Mar 01 '16 at 17:01

4

Just check the version of Newtonsoft.Json Newtonsoft properties

Then you need to add that version in your web config (in my case 8.0.0.0) Web config

answered Mar 01 '16 at 17:01

Gerald Padgett E.

51
5

score 3 · Answer 22 · answered Jul 29 '14 at 14:53

I made the mistake of adding a NewtonSoft .dll file for .Net 4.5.

My main project was 4.5, but when I added an extra project to my solution, it strangely added it as a .Net 2.0 project... and when I attempted to use NewtonSoft's 4.5 dll with this, I got this "Newtonsoft.Json couldn't be found" error.

The solution (of course) was to change this new project from .Net 2.0 to 4.5.

score 3 · Answer 23 · edited May 18 '15 at 16:57

3

I was facing the same error and struggled with it for hours. I had a web API project which is using Newtonsoft.json and another UnitTest project for the web API project. The unit test project also needed the Newtonsoft.json reference. But on adding the link I was getting the above exception.

I finally resolved it by adding the below code snippet in the app.config of the unit test project:

<dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30AD4FE6B2A6AEED" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
</dependentAssembly>

edited May 18 '15 at 16:57

Brian

14,610
7
35
43

answered May 18 '15 at 13:06

mukulsharma1146

171
1
2
12

– mukulsharma1146 May 18 '15 at 13:06
I was having this same problem when I upgraded Nestwonsoft.Json while still using and old version of WebAPI, and this solved it. Thanks! – Gabby Paolucci Jun 17 '15 at 14:50

score 3 · Answer 24 · answered Jul 27 '15 at 07:49

3

In my case, the main project was still referencing an old version of Newtonsoft.Json which didn't exists in the project any more (shown by a yellow exclamation mark). Removing the reference solved the problem, no bindingRedirect was necessary.

answered Jul 27 '15 at 07:49

IngoB

2,552
1
20
35

lazizanie · Answer 25 · 2015-10-26T15:01:16.657

I had the exact same problem with version 7.0.0.0, and the lib causing my problem was Microsoft.Rest.ClientRuntime which somehow was referring to the wrong version (6.0.0.0) of Newtonsoft.json, despite the right dependency management in nugget (the right version of newtonsoft.json (7.0.0.0) was installed).

I solved this by applying the redirection above from 6.0.0.0 to 7.0.0.0 (from Kadir Can) in the config file:

<bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="7.0.0.0" />

----> After a few days without changing anything it came up again with the same error. I installed version 6.0.0.0 n updated it to 7.0.0.0 it works fine now.

Worked for me. Installed version Newtonsoft Json 7.0.1 (beta), but the config generated was pointing to 6.0.0.0 which was not correct. Thanks! — Dhanuka777, Nov 05 '15 at 02:36

score 3 · Answer 26 · answered Nov 27 '15 at 16:53

3

Reinstall newtonsoft package through nuget did not worked for me. I had to manually call JsonConvert.DeserializeObject to bypass this issue

I changed

HttpResponseMessage response = await client.GetAsync(url));
response.EnsureSuccessStatusCode();
MyObject data = await response.Content.ReadAsAsync<MyObject>();

For

HttpResponseMessage response = await client.GetAsync(url));
response.EnsureSuccessStatusCode();
string jsonStr = await response.Content.ReadAsStringAsync();
MyObject data = JsonConvert.DeserializeObject<MyObject>(jsonStr);

answered Nov 27 '15 at 16:53

Bioupy

31
2

1

I have found that instead of calling the JsonConvert.DeserializeObject() directly, you can add the Microsoft.AspNet.WebApi.Client package from NuGet to get the updated version of System.Net.Http.Formatting. This will allow you to use the response.Content.ReadAsAsync() call and let Json.Net work behind the scenes. – Brian Behm Dec 15 '15 at 21:18
Bioupy, your suggession worked for me. In my project we use Newtonsoft.Json version=9.0.0.0 (as a NuGet package) and Microsoft.AspNet.WebApi.Client version=5.2.3 (also as NuGet). It seems that the System.Net.Http.Formatting.dll has a strict version reference to Newtonsoft.Json.dll of version=6.0.0.0. So it tried to load version 6.0.0.0, but I couldn't put 2 Newtonsoft.Json assemblies of 2 different versions in my application target folder. So reading the response as string and deserializing it with JsonConvert.DeserializeObject resolved my case. – VitaliG Apr 12 '17 at 10:38

score 2 · Answer 27 · answered Apr 10 '14 at 14:17

In my case, after downloading the assembly and adding the reference to the project, I solved this by 'unblocking' the DLL before adding the reference to the project.

Using Windows explorer, browse to the DLL location, right-click on the DLL and then select 'properties'. You'll find an 'unblock' button on one of the tabs and then you can add the reference and the assembly will load correctly.

valentinvs · Answer 28 · 2015-01-27T13:45:47.007

2

Nothing from above helped me, but what actually fixed it is the following:

Remove all dependency bindings in app.config (from all app.config files in the solution)
Execute the following command from "Package Manager Console"

Get-Project -All | Add-BindingRedirect

Rebuild

Reference: http://blog.myget.org/post/2014/11/27/Could-not-load-file-or-assembly-NuGet-Assembly-Redirects.aspx

edited Jan 27 '15 at 13:45

answered Jan 27 '15 at 12:27

valentinvs

191
1
6

score 2 · Answer 29 · answered May 07 '15 at 14:56

2

Right click your project select manage Nuget packages, type newtonsoft in the search box and install the latest version. Then Run your App

answered May 07 '15 at 14:56

uche Godfrey

111
1
6

score 2 · Answer 30 · answered Aug 18 '15 at 14:08

Another insidious problem is that it appears that binding redirects can just silently fail if the element has an incorrect configuration on any other dependentAssembly elements.

Ensure that you only have one element under each element.

In some instances, VS generates this:

  <dependentAssembly>
    <assemblyIdentity ...
    <assemblyIdentity ...
  </dependentAssembly>

Instead of

  <dependentAssembly>
    <assemblyIdentity ...
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity ...
  </dependentAssembly>

Took me a long time to realise this was the problem!

score 2 · Answer 31 · answered Sep 04 '15 at 05:42

Below section add in to your web.config

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
       <dependentAssembly>
           <assemblyIdentity name="Newtonsoft.Json"
               publicKeyToken="30AD4FE6B2A6AEED" culture="neutral"/>
           <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0"/>
       </dependentAssembly>
    </assemblyBinding>
</runtime>

score 2 · Answer 32 · answered Sep 09 '15 at 06:26

2

If error disappears locally and still appears on server, the solution that works with me is to delete bin folder and packages.config and web.config and reupload these files

answered Sep 09 '15 at 06:26

Ahmad Alaa

767
9
30

score 1 · Answer 33 · answered Jul 03 '14 at 07:46

1

The problem for me was a depreciated version of Newtonsoft.Json. Re-installing didn't help.

In Visual Studio, go to Tools->Manage NuGet Packages. Select Updates. Search for Newtonsoft. Click Update to install the latest version.

answered Jul 03 '14 at 07:46

spadelives

1,588
13
23

The latest version isn't always the right approach - for us v6 broke some inherited serialisation that had worked just fine in v4. – Mark Cooper Jul 21 '14 at 06:57
You can always revert back to the old version if you experience side effects. – spadelives Jul 21 '14 at 20:01

score 1 · Answer 34 · answered Jan 27 '15 at 23:26

Also, in a CI environment with NuGet restore, be sure that you don't have partial folders checked into source control. By default, when adding folders to source control, it will automatically exclude assemblies. Besides, this defeats the whole purpose of restoring nuget packages upon build. Either checking assemblies, or not checking in any packages folders will get a successful build, but the better practice is to not check nuget packages into source control.

score 1 · Answer 35 · answered May 17 '16 at 05:14

1

I solved this issue by installing the Nuget package: Microsoft ASP.NET Web API 2.2 Client Libraries. This in turn installed newtonsoft.json version 6.04

answered May 17 '16 at 05:14

JohnnyBT

41
3

score 1 · Answer 36 · answered Feb 09 '18 at 14:17

One more advice to the open topic. The error appears after running the "Analyze": something was changed in the project settings. The problem was that in:

Project / Settings / Build / Platform target

appeared "Any CPU".

Setting back to x86 (or maybe x64 in your case) solved the issue.

score 1 · Answer 37 · answered Feb 27 '18 at 06:00

updating web.config with the following assembly binding resolved the issue 
<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">     
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed"
                culture="neutral" />
        <bindingRedirect oldVersion="4.5.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

score 1 · Answer 38 · edited Sep 19 '20 at 09:06

1

For a simplest solution you can set your project file to automatically generate binding redirects for you:

<PropertyGroup>
     <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
</PropertyGroup>

https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/how-to-enable-and-disable-automatic-binding-redirection

edited Sep 19 '20 at 09:06

Martijn Pieters

1,048,767
296
4,058
3,343

answered Dec 20 '19 at 11:21

Vedran

10,369
5
50
57

score 1 · Answer 39 · answered Jan 07 '22 at 01:21

I wrote a program to fix this automatically. It will ensure that your program is able to use the latest version of the target assemblies on your hard drive, not just the ones your dependent libraries want.

https://github.com/BackTrak/DependencyFixup/releases/tag/1.0.0.0

No more guessing, it will fix all the manifest reference issues for you automatically.

score 0 · Answer 40 · answered Jan 04 '16 at 06:43

You can find the installed version of ur library from the properties inside references. For my case i had 8.0.0.0 installed. Error says Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies.

So i had to add the following manually inside web.config

  <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" />
        <bindingRedirect oldVersion="6.0.0.0-8.0.0.0" newVersion="8.0.0.0" />
      </dependentAssembly>

score 0 · Answer 41 · answered Oct 05 '16 at 00:38

0

I've been struggling with it for a day or so too, tried every solution. What helped me was to check that capital letters in app.config. I had PublicKeyToken instead of publicKeyToken, after changing it suddenly worked.

answered Oct 05 '16 at 00:38

Igor Be

898
7
17

score 0 · Answer 42 · answered Jun 20 '17 at 08:38

Apart from many answers here,I found something hence adding it.First point,Make sure the dll is not referenced from GAC.Apart from this,

While adding/changing dll of Newtonsoft.Json ,Sometimes *.csproj of the project doesnt get changed or the changed version of json dll will not be reflected in csproj of the solution.

So Open the project in notepad++ and search Newtonsoft.Json and rename the JSON from old version to New version explicitly.Now after tabbing back to VS ,the solution/project will reload with needed version Newtonsoft.JSON dll.

score 0 · Answer 43 · answered Nov 27 '18 at 15:00

0

In my case I had folder name Newtonsoft.Json.6.0.7

but .csproj file had path though folder ...\Newtonsoft.Json.6.0.5\...

Changing .csproj file to have 6.0.7 fixed the problem.

answered Nov 27 '18 at 15:00

Vanity Slug - codidact.com

1,347
1
16
31

score 0 · Answer 44 · answered Apr 16 '20 at 04:54

This is very old, seems still many people having issues with the same thing. So I would like to share my experience that it might help someone.

I had the same issue in two places. In one project users 6.0.4.0 and in different project use 4.5.0.0.

1- This work for me. In bin folder I have 6.0.0.0 Newtonsoft.Json.dll and symbolic link to 4.5.0.0 dlls

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<probing privatePath="bin\4.5dlls-path;" />
<assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" 
culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>

If you don't know how to create symbolic link here.

mklink /D "name of the folder" "Path to the dll"

2- In this case when I remove the secion from Web config file it worked. Remember I have reference to 6.0.0.0 and 4.5.0.0 in different projects. In symbolic link I had 12.0.1.0 dll and bin 6.0.0.0.

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<probing privatePath="bin\12.0.1dlls-path;" />
</dependentAssembly>
</assemblyBinding>
</runtime>

3- I have one more solution. If you have different versions of Newtonsoft.Json.dll in different projects try to upgrade all into one version or to the latest version, But in some case it might not work. Ex: System.Net.Http.Formatting.dll might need the version of Nettonsoft.Json.dll 6.0.0.0. In this case you need the vision 6.0.0.0, so try to make all into same version. Hope this might help some one.

score 0 · Answer 45 · answered Jun 16 '20 at 21:04

I had the same issue and I got the exception when I was trying to create MassTransit queues:

"Exception: System.TypeInitializationException: The type initializer for 'MassTransit.Serialization.JsonMessageSerializer' threw an exception. ---> System.IO.FileLoadException: Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)"

Solution that worked for me (after spending couple of days reverting several commits):

We had a windows service solution that has .Service project and .XUnitTests project. Both of them were using a common nuget that has dependency on Newtonsoft.Json.dll. There was no explicit reference to Newtonsoft.Json nuget package in both projects (but we were using 'using Newtonsoft.Json;' namespace in our classes), so the common nuget was using version 9 of Newtonsoft.Json by default.
As soon as I installed the Newtonsoft.Json nuget in both .Service and .XUnitTests projects, the common nuget package started using the latest v12 Newtonsoft and that fixed my issue.

Just posting it in here if it saves anyone their valuable time.

score 0 · Answer 46 · answered Jun 21 '22 at 19:42

Answer from 2022. Was getting a similar exception error to this:

Could not load file or assembly 'Newtonsoft.Json, Version=13.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'

The fix was to go into Web.config file for the project and make the following edits:

<dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed"
        culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="11.0.0.0" />
</dependentAssembly>

Could not load file or assembly 'Newtonsoft.Json, Version=4.5.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'

46 Answers46

Linked

Related