We have moved to GitHub Issues
Created by firepol 17 Apr 2014, 14:15:30 Updated by Sebastiaan Janssen 05 Jun 2015, 16:28:23
I tried to upgrade umbraco cms core (having 6.1.6 already installed) nuget package and couldn't because of the json.net wrong dependency. JSON.net 5.0.6 already installed.
The only way to upgrade via nuget was: Install-Package UmbracoCms.Core -Version 6.2.0-RC -Prerelease -IgnoreDependencies
Please fix it in the final 6.2 release (like you did for umbraco 7.x I read somewhere json.net dependencies were also an issue). THX
If you get this error it means that you've tried to install Umbraco in a MVC5 project, which comes with json.net 5. We do not support MVC 5 yet.
However, I've losened up the json.net dependencies so now you can install json.net v6 if you want with your umbraco project.
Steps to reproduce. Create a new empty Visual Studio solution (select framework: .net 4.5). Add new project, I select "MVC 4 Webapplication". Select "Empty application".
Via NuGet console: Install-Package UmbracoCms -Version 6.2.0
I get this error: Install-Package : Already referencing a newer version of 'Newtonsoft.Json'.
To fix: Install-Package -IgnoreDependencies UmbracoCms -Version 6.2.0
Then it works.
No, wait, actually it works only if I uninstall Newtonsoft.Json:
Uninstall-Package Newtonsoft.Json -Force
Then I can install UmbracoCms or UmbracoCms.Core without the Json problem...
Anyway, as you can see, this is not yet fixed, at least when using NuGet. Maybe fix in 6.2.1?
@firepol No, I'm sorry, I don't get this error with the steps you list.
Mmmh then it must be only on my particular Visual Studio 2012 installation (I modified the MVC 4 templates to get some newer versions of the libraries, see here: http://www.pbworks.net/visual-studio-2012-templates/ ), that may be the cause). Well if nobody else complains it's really a problem affecting my computer only -I will test on a frash Visual Studio 2012 installation anyway, to be sure-, sorry about that ;) I posted an easy solution (uninstall Json.Net with the -Force flag) in case somebody has the same issue.
Backwards Compatible: True
Due in version: 6.2.0