The latest stable version of a NuGet package PACKAGE is easily located via the generic URL
https://www.nuget.org/packages/PACKAGE/
Is there a generic URL analogue to the latest pre-release version of the same NuGet package?
Adding absoluteLatest like https://www.nuget.org/packages/PACKAGE/absoluteLatest seems to work these days.
Finally got a response to this question on the NuGet Gallery issues section on Github. Thanks, Maarten Balliauw!
Maarten's response: (slightly modified to sync with the original question)
There is no such URL currently. You could use the API to query for the latest prerelease of a package though, for example:
https://www.nuget.org/api/v2/FindPackagesById()?Id=%27PACKAGE%27&$filter=IsPrerelease&$orderby=Version%20desc&$top=1
From this response, you can get the package URL.
Related
I am trying to find Microsoft.TeamFoundation.Framework.Common. I can't find it in Nuget or in the files for Visual Studio. We currently use version 2018 of TFS.
Before anyone tells me to download the Nuget package for Microsoft.TeamFoundation.Common, I get the following message when I try to do so:
The owner has unlisted this package. This could mean that the package is deprecated, has security vulnerabilities or shouldn't be used anymore.
I can find Microsoft.TeamFoundation.Common.dll in the TFS Server files, but that does not help me with Microsoft.TeamFoundation.Framework.Common. I still get messages such as:
BC30456 'CatalogQueryOptions' is not a member of 'Microsoft.TeamFoundation.Framework.Common'.
The Microsoft.TeamFoundation.Framework.Common is now deprecated by Microsoft. You can still download older packages, but it only can only be used in Team Foundation Server 2015.
Click this link for the old version of Microsoft.TeamFoundationServer.Client package. And then, you can use the Microsoft.TeamFoundation.Framework.Common namespace which is included in it.
How can I get library for Microsoft.Practices.CompositeWeb.WebClientApplication I cannot find it in nuget. I have a copy of v3.0.0.0, is there any latest version after that? Does Microsoft support it anymore?
I found this article online https://msdn.microsoft.com/en-us/library/ff709858.aspx
it says its retired content, and not mentioned where to download it from.
Comments for the v3 api was just released. We're using the .net client library and as far as I can tell the new comments changes are not included in the latest dlls. Does anyone know when the changes will be included in the libraries?
I'm just trying to figure out if it's worth creating my own wrapper or not. Thanks!
I just uploaded the new v3 version to NuGet.
I run the NuGet publisher once a week to update all Google.Apis packages. I already ran it this week, but with your request I just ran it again.
Following the documentation described in this link, I'm trying to install the Breeze with NHibernate support.
But the Breeze.Server.ContextProvider.NH does not exist, what should I do? What are the steps to use Breeze with NHibernate?
The Breeze.ContextProvider.NH source and dll is available on GitHub, but we are still in testing on it, so we haven't created a nuget package for it yet.
The nuget package is now available, and the NorthBreeze sample
is now updated to use Breeze 1.4.8 and WebApi 2
I updated the sample by removing all the existing references, then installing the nuget package Breeze.WebApi2.NH
Except for some using statements, and one redundant line of the Web.config, I didn't need to change any code.
Okay, so help me understand something here. I've got a new MVC solution and want to use NuGet to keep Modernizr up to date.
The problem is, NuGet puts the Modernizr scripts under ~/Scripts. This won't work--we've decided to put our JS in ~/js.
How do I modify the configuration of this package to tell NuGet that the Modernizr package should go in ~/Scripts or ~/Scripts/global instead?
I don't think you can do this - I don't think this is functionality of NuGet, but rather the location of the scripts inside the NuGet package. This could vary from one package to another :-(
This is currently not a feature of NuGet, but it was mentioned in discussion on the a NuGet forums including members of the NuGet team. I don't see any work item that has officially been created for this yet, unfortunately. I performed a quick search of the NuGet issues list for the word "location" and didn't see one out there for this. You might want to request it as a feature.