I know that to always use a latest nuget package in my client project, I need to do things such as:
<ItemGroup>
<PackageReference Include="MyServerNugetPackage" Version="2.*" />
So this will force my project to take the latest version 2 nuget package. As I am both the consumer and creator of the nuget package, the QA team wants that certain branch of my client project, I should consume the latest preview version of the nuget package (So they can test the preview functions in the nuget package before other teams consume them).
As my knowledge goes, "2.*" will return the latest stable version of nuget package and I am not really aware if it is possible to get latest preview version. Can it be done?
See this article
Support pre release packages with floating versions
Related
In my class library, Manage Nuget Packages shows the latest stable version of Newtonsoft as 12.0.3. In another application that references the class library, Manage Nuget Packages shows the latest stable version of Newtonsoft as 9.0.1
What would explain that difference, and how is it fixed in Visual Studio 2019? When I try to compile the application, it fails with the error that the class library's version of Newtonsoft is newer.
EDIT: I think I've found the reason: in the top right corner of the window the package source for the application was not nuget.org but Visual Studio Offline Sources.
Why is the latest stable version of Newtonsoft showing in Nuget
Package Manager as 12.0.3 in one project and as 9.0.1 in another?
When you install a nuget package, you should select the right nuget package source.
As it shows that, Visual Studio Offline Sources is your local nuget caches. It is required that you download the corresponding nuget version and then exist in this data source. So it depends on you and not all versions of the package are fully displayed.
nuget.org is the ultimate destination for developers releasing nuget packages. You can find every version of the package here. So you should check this link.
Check and enable that link.
Then, open Nuget Package Manager UI and choose nuget.org and you can find it.
VS 2017, monogame project, pulled in the MonoGame.Extended.Entities dependency. I went to the class browser and I don't see the world object. I can see it's apart of the code on github and should be there.
I installed the dependency through the nuget manager in vs 2017.
using version 1.1.0 MonoGame.Extended.Entities
I had this issue as well. The demos on their GitHub page all function normally, and they reference the source code, not the nuget packages, so the night versions are lacking . The 1.1.0 nuget version doesn't appear to match the GitHub version 1.1.0, which is a little unusual. I fixed it by updating the packages to the prerelease version. The method I used can be found in their docs:
http://docs.monogameextended.net/NuGet-Pre-Release/
I am working on VS2012 and have issue with installing Twilio Package via NuGet. It asks me to update NuGet Package Manager. I am concerned if updating NuGet Package Manager have effect on all the projects that are running without any issue. What are the effects of Package Manager Updates on existing projects or solution.
Coming from the Python world, I will attempt to see if I can help you here. Is the concern that a specific package will no longer be available to you if you do a global update on your NuGet package manager?
Is it possible then for you to install a specific NuGet version in a virtual machine encapsulating the project where you want to run with the Twilio package?
Otherwise, assuming all of the packages you use are regularly maintained, I'm not sure how an update to a package manager would affect them.
Using team city as our CI and I've started getting this error message. We've obviously updated System.Net.Http recently which now needs a new version of NuGet. How do I get team city to find the new NuGet version. I've tried installing VS2015 and updating NuGet package manager through there. I've tried pointing directly to the command line nuget.exe (Don't know if that's been updated to v3?)
[restore] The 'System.Net.Http 4.0.0' package requires NuGet client version '3.0' or above, but the current NuGet version is '2.8.60717.93'.
[restore] Process exited with code 1
Do I just have to just wait till MS pushing the new nuget package to nuget?
Thanks
On your teamcity client you can configure the nuget versions available to your build agents.
Go to Administration -> Integrations -> NuGet
From this screen you can click Fetch NuGet and retrieve the latest version. Then you should be able to specify that version on your build step.
Download NuGet 3.1 from this url:
http://dist.nuget.org/win-x86-commandline/v3.1.0-beta/nuget.exe
Then put that on your build server, put the directory in your path, and run your NuGet build steps as "Command Line" commands in TeamCity, using NuGet.exe.
I think you need TeamCity 9.1, as that version contains the VS2015 build tools: https://confluence.jetbrains.com/display/TCD9/What%27s+New+in+TeamCity+9.1
NuGet 3.0 was released with VS2015: http://docs.nuget.org/release-notes/nuget-3.0.0
In earlier versions of Visual Studio you could add a System reference to System.Net.Http, but Microsoft has now moved that into a NuGet package.
Successfully building and publishing my own NuGet packages via a batch script, I would love to automatically unlist all previous versions when uploading a new version of my package.
What I'm currently doing is to manually use the web browser and unlist the previous versions.
So my question:
Is it possible to automatically unlist all previous versions when publishing a new NuGet package version?
If you know the version numbers of the old versions you want to delete/unlist you should be able to script calls to NuGet delete.
NuGet.exe delete <package Id> <package version> [API Key]