Umbraco 7.1.1 Updating Microsoft.AspNet.WebApi.Client to 5.1.2 failed
Hi Guys,
I'm new at developing in umbraco(using 7.1.1 version),
i tried to update the web api client package with no success.
Updating 'Microsoft.AspNet.WebApi.Client 4.0.30506.0' to 'Microsoft.AspNet.WebApi.Client 5.1.2' failed. Unable to find a version of 'UmbracoCms.Core' that is compatible with 'Microsoft.AspNet.Web Api.Client 5.1.2'.
MVC 5 has breaking changes, causing all sorts of dependency issues with various NuGet and other 3rd party Umbraco packages.
We don't know what would be involved, we haven't tested any further then: if someone upgrades umbraco then their site breaks, which we never want to do. We will look into moving to MVC5 when we start working on version 8, for which we have no date set but it is at least a few months off.
Umbraco 7.1.1 Updating Microsoft.AspNet.WebApi.Client to 5.1.2 failed
Hi Guys,
I'm new at developing in umbraco(using 7.1.1 version),
i tried to update the web api client package with no success.
Updating 'Microsoft.AspNet.WebApi.Client 4.0.30506.0' to 'Microsoft.AspNet.WebApi.Client 5.1.2' failed. Unable to find a version of 'UmbracoCms.Core' that is compatible with 'Microsoft.AspNet.Web
Api.Client 5.1.2'.
Please advice
Please make sure to install umbraco into a MVC4 project, MVC5 is not yet supported.
http://our.umbraco.org/documentation/installation/install-umbraco-with-nuget
Hi Sebastiaan,
Are there technical reasons for not supporting MVC 5? Im having all sorts of dependency issues too with various NuGet and other third-party packages.
What would be involved in making the leap to MVC 5?
MVC 5 has breaking changes, causing all sorts of dependency issues with various NuGet and other 3rd party Umbraco packages.
We don't know what would be involved, we haven't tested any further then: if someone upgrades umbraco then their site breaks, which we never want to do. We will look into moving to MVC5 when we start working on version 8, for which we have no date set but it is at least a few months off.
is working on a reply...