I'm getting the following error while installing the Breeze Server for Web API 2.0.
Updating 'Microsoft.AspNet.WebApi.Core 5.2.0' to
'Microsoft.AspNet.WebApi.Core 5.1.0' failed. Unable to find a version
of 'Microsoft.AspNet.WebApi.WebHost' that is compatible with
'Microsoft.AspNet.WebApi.Core 5.1.0'.
Any help is appreciated.
I had similar issue with Visual Studio 2013 Update 3.
Installed Microsoft.AspNet.WebApi.OData first and Breeze.Server.WebApi2 both via NuGet
That issue did not appear. For now lets take that as a quick fix.
You must install Breeze.Server.WebApi2 before installing Microsoft.AspNet.WebApi.WebHost.
* EDIT *
This NuGet versioning issue has been fixed in Breeze v1.4.17 (i.e. for the current Microsoft.AspNet... NuGet packages)
* EDIT *
The issue is not with Breeze.Server.WebApi2, but with the Microsoft.AspNet.WebApi.OData package.
Breeze.Server.WebApi2 NuGet package requires Microsoft.AspNet.WebApi.OData with version ≥ 5.1 && < 6.0.
If you install the Breeze.Server.WebApi2 and Microsoft.AspNet.WebApi.OData is not already installed, it will install the base version (5.1) and not the latest.
The issue is that Microsoft.AspNet.WebApi.OData 5.1 depends on Microsoft.AspNet.WebApi.Core version ≥ 5.1.0 && < 5.2.0.
That conflicts with Microsoft.AspNet.WebApi.WebHost 5.2 (which you have installed in your solution) as it depends on Microsoft.AspNet.WebApi.Core version >=5.2 and <5.3.
So, when Microsoft.AspNet.WebApi.OData is trying to be installed, it will try to roll Microsoft.AspNet.WebApi.Core version to 5.1 and that will fail because Microsoft.AspNet.WebApi.WebHost depends on a newer version.
All this is happening because Breezejs 1.4.16 was tested with Microsoft.AspNet.WebApi 5.1 as version 5.2 had not yet been released at the time.
We will update version dependencies on our NuGet packages in the coming release, but this problem is still meant to reoccur in the future as we have no control as to how Microsoft will set their packages dependencies in their coming releases.
The previous workaround is overwork though, as you can simply install the latest Microsoft.AspNet.WebApi.OData package (5.2) before installing Breeze.Server.WebApi2.
Microsoft.AspNet.WebApi.OData 5.2 will fulfill the Breeze.Server.WebApi2 dependency and you won’t have installation errors or to deal with the hassle of uninstalling/installing a bunch of packages.
Related
Though I've published a new version of one of dependent library but when I am installing that using the yeoman generator it is installing -1 version than the current version. I don't know where is the issue.
Installing the package XPlot.Plotly (v. 1.4.2) using Nuget failed with a message that there was incompatibility with the latest version (v. 10.0.3) of Newtonsoft.Json, which I had installed previously. The message also indicated that version 9.0.1 of Newtonsoft.Json would work. So I uninstalled the latest version of Newtonsoft.Json, installed version 9.0.1, and then was able to install XPlot.Plotly.
Is this the correct way to deal with this type of incompatibility?
Will I eventually be able to use the latest versions of both packages?
Every time I install a new bower package on my Ember CLI pack, I got
Missing bower packages:
Package: ember
* Specified: 1.11.0
* Installed: 1.10.0
then I run bower install ember#1.11.0.
Unable to find a suitable version for ember, please choose one:
1) ember#1.10.0 which resolved to 1.10.0 and is required by test-addon
2) ember#>= 1.8.1 < 2.0.0 which resolved to 1.11.0 and is required by ember-data#1.0.0-beta.16
3) ember#> 1.5.0-beta.3 which resolved to 1.11.0 and is required by ember-resolver#0.1.15
4) ember#>=1.4 <2 which resolved to 1.11.0 and is required by ember-cli-shims#0.0.3
5) ember#1.11.0 which resolved to 1.11.0Prefix the choice with ! to persist it to bower.json
I choose 5 (Why this hassle if I explicit added the desired version), then it works again.
But next time if I install a new bower package, I have to do it again.
node 0.12.1
bower 1.3.12
emvber cli 0.2.2
You may use -F flag to force to use latest version:
bower install -F
(see docs)
In this case bower didn't asking anything about versions.
I'm installing plugins using bower, but bower only downloads Footable v2.0.1, not the latest release of v2.0.1.5.
I've tried:
bower install --save-dev footable
bower install --save-dev footable#2.0.1.x
Both these download v2.0.1, I want the latest tagged release of v2 (v2.0.1.5).
Using #2.0.1.x also gave the error "ENORESTARGET: Tag/Branch 2.0.1.x does not exist".
Bower package versions should follow semantic versioning.
In short, a valid semantic version is in the form of MAJOR.MINOR.PATCH.
2.0.1.5, for example, is not a valid semantic version.
You can get a list of available versions for a package by running the following command:
bower info footable
For footable you the results are:
Available versions:
- 2.0.1
- 2.0.0
- 0.5.0
- 0.1.0
I have package bootstrap-calendar
In bower.json it is version 0.2.0-RC and I even updated it to 0.2.0. But no matter what when you run
$> bower install bootstrap-calendar
it attempts to install version 0.0.9 which is earliest version. I cleaned cache but no success. What can I do that on bower install command latest package would be installed?
I don't think this is anything you are doing incorrectly. The package installs for me as 0.0.9 and the js file is listed as 0.1. I think the package is just not correct and needs to be mentioned on the issues section of Github, which I did.