How do I sort out my web.config that is giving me Json issues

Question

0.00/5 (No votes)

See more:

How do I sort out my web.config that is giving me Json issues

It gives me an error that reads: "Could not load file or assembly 'Newtonsoft.Json' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference".

Please assist on how I can solve this issue.

Posted 27-Jul-15 11:03am

Phiwa256

Add a Solution

Comments

F-ES Sitecore 27-Jul-15 17:55pm

Have you used nuget to install Newtonsoft Json? Is the assembly in the bin folder?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mr Ellipse · Answer 1 · 2015-07-27T17:15:00

Your compiled code is different from the version the runtime is trying to load.

The compilation process is creating an assembly with reference to version Newtonsoft.XX.dll - but at runtime the bin folder of your website probably contains a different version Newtonsoft.XY.dll.

You can make sure the runtime and design time assemblies used are the same - cross check properties of references in your Visual Studio project against the files produced by publishing your website - to figure out why the runtime cannot load up correct version.

Or you can look into adding Assembly Binding Redirection[^] instructions in the web.config file.