title: Can I install ravendb client alongside Microsoft.AspNet.WebApi.Client?
body: <p>I'm trying an ASP.NET MVC4 Web API project. I'm trying to install the ravendb client through nuget. This is the error:</p>
  
  <pre><code>Attempting to resolve dependency 'NLog (= 2.0.0.2000)'.
  Successfully installed 'Newtonsoft.Json 4.0.8'.
  Successfully installed 'NLog 2.0.0.2000'.
  Successfully installed 'RavenDB.Client 1.0.960'.
  Install failed. Rolling back...
  Updating 'Newtonsoft.Json 4.5.1' to 'Newtonsoft.Json 4.0.8' failed. Unable to find a version of 'Microsoft.AspNet.WebApi.Client' that is compatible with 'Newtonsoft.Json 4.0.8'.
  </code></pre>
  
  <p>So I can see that Microsoft ASP.NET Web API Client Libraries (I think this is what I have installed: <a href="http://nuget.org/packages/Microsoft.AspNet.WebApi.Client" rel="nofollow noreferrer">http://nuget.org/packages/Microsoft.AspNet.WebApi.Client</a>) has a dependency on Newtonsoft.Json (≥ 4.5.1)</p>
  
  <p>And this says the ravendb client install requires (= 4.0.8) <a href="http://nuget.org/packages/RavenDB.Client/1.0.960" rel="nofollow noreferrer">http://nuget.org/packages/RavenDB.Client/1.0.960</a></p>
  
  <p>So I've looked and this question is very similar: <a href="https://stackoverflow.com/questions/7908760/nuget-package-dependencies-does-it-work-the-way-it-should">Nuget package dependencies. Does it work the way it should?</a> but this is a bit older and looks like the problem there is different- here Raven does actually seem to need Newtonsoft.Json 4.0.8</p>
  
  <p>So my question is, is this possible? Is there some way (maybe from the command line/ through the console) that I can get these 2 things installed side by side. How can I get Microsoft.AspNet.WebApi.Client to play nicely with Newtonsoft.Json?</p>
  
  <hr>
  
  <p><strong>EDIT:</strong> This problem and solution are obsolete. There have been <a href="http://builds.hibernatingrhinos.com/builds/RavenDB" rel="nofollow noreferrer">four stable RavenDB builds</a> since this question was posted. The latest stable build will in fact fix this issue, and one should not experiment with an unstable build simply to fix this problem.</p>