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.
Related
I am releasing private cocoapod versions by using github. Here problem is If i release new version, old version is not working. I mean user is unable to install old version of my Pod.
Ex: New version is 1.2.3
Old version is 1.2.2
User can't able to install 1.2.2 version. Please help me how to maintain all versions.
Thanks in Advance.
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?
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'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.
I am trying to upgrade my ruby version that came with my rails installer on my windows machine but i failed to figure it out. Do i need to re-download the whole railsinstaller package and move my project to this new package or could anyone have an easier way of doing this upgrade through the command prompt.