This is not the first time it has happened, so I assume it's a bug where in the pipeline of NuGet Client / Visual Studio / NuGet server. A package has just been updated on NuGet.org. The latest version is 3.0.0.14. When I went to upgrade my package it couldn't find it and it said I had the latest version. After using Fiddler to see what was going over the wire, it's clear the NuGet Server is not serving the latest information. This call returns version 3.0.0.13 as the latest version.
https://api.nuget.org/v3/registration1/tweetmoasharp/index.json
Is that a bug on NuGet Server? Do they have a deliberate caching? Is it something the package publisher did that he didn't mark as a stable version?
Related
We have an .Net 6 API.
We have our own Nuget server to ensure we have backup of used Nuget packages so we always are sure we can run our CI chain.
After the upgrade to .Net 6, then every time MS publishes a new version of any of these three assemblies then our CI builds fail, because our NuGet server doesn't have the new version.
Microsoft.NETCore.App.Runtime.win-x64
Microsoft.AspNetCore.Runtime.win-x64
Microsoft.WindowsDesktop.Runtime.win-x64
Latest with 6.0.8. We then have to download the new packages to our Nuget server and then everything works.
In general I would like us to keep on known versions all the time, and only change referenced package version on purpose - and not just because developers publish new versions.
But I can't find any explicit references to these three packages.
Does anyone know where they come from - and more importantly - are there any way to lock our solution to use e.g. 6.0.8, until we decide to upgrade next time?
Best regards
/Anders
Suppose I have version 1.1.0 on a NuGet server.
I then continue development and push version 1.2.0.
Then I find a bug in version 1.1.0 and want to fix this.
At this point, can I still push version 1.1.1?
There's nothing in the NuGet spec or protocol that prevents it, so it might depend on which NuGet server you're using, but I would be extremely surprised if any server forbids it because it would be so short sighted, in my opinion.
Using NuGet.Protocol on nuget.org as an example, version 4.9.3 was release in January 2019, but versions 4.8.2, 4.7.2, 4.6.3, 4.5.2, 4.4.2 and 4.3.1 were released in March, two months later.
I've created a simple Azure Mobile Services project and added the nuget package for MongoDB (package id is mongocsharpdriver).
The version I added is 1.10.0
When I deploy the project I get the following error:
"Found conflicts between different versions of the same dependent assembly 'MongoDB.Bson': 1.10.0.62. Please change your project to use version '1.9.2.235' which is the one currently supported by the hosting environment."
It seems like the Dlls from the package I've added are conflicting with an older version installed by default in the cloud environment.
Is there a way to get around this problem?
(While trying to figure out whats wrong I installed the nuget package WindowsAzure.MobileServices.Backend.Mongo which can't be installed because it requires mongocsharpdriver(=1.9.2) and dose not allow me to use my newer dlls.)
It seems I'll have to wait for microsoft to update the dll in Azure:
On multiple sources in internet i see that SignalR 0.5.3 is released, i even find the screenshot of NuGet Manager which has v 0.5.3 on it.
But in my Nuget manages there is only v 0.5.2 and here also latest is 0.5.2.
So, the question is where do i get the latest SignalR?
It seems like 0.5.3 is on the gallery, just hasn't been tagged as the newest release.
http://nuget.org/packages/SignalR/0.5.3
Try running this in the Package Manager Console:
Install-Package SignalR -Version 0.5.3
However, I suspect that 0.5.3 has been pulled because of a problem (?) since the official SignalR web site says 0.5.2 is the latest. It might also be that they are going to rename the NuGet package to Microsoft.AspNet.SignalR.
I have a "new" windows xp sp3 machine with VS2010 SP 1 and Nuget 1.8
Every time a try to add a Nuget Package a receive the following error:
The specified cryptographic algorithm is not supported on this platform.
Does anyone know what does that means?
There's a known issue with NuGet 1.8 : NuGet issue#2240. The Nuget team will soon (crossing fingers) release a hot fix.
In the meanwhile, I'd suggest installing NuGet 1.7.
EDIT: NuGet released the hotfix (1.8.30524.9000)