visual-studio-2005,nuget,nuget-package-restore
Change the Action combobox value from install to Update/Upgrade ...
nuget,nuget-package,nuget-package-restore
The Host Build Controller on Visual Studio Online now performs NuGet implicitly. It does not have the same problem!
nuget,dependency-management,asp.net-5,nuget-package-restore
Apparently ASP.NET vNext dropped support for running *.ps1 scripts in NuGet packages http://forums.asp.net/p/2027698/5842272.aspx
.net,tfsbuild,tfs2013,xunit.net,nuget-package-restore
Finally I resolve that problem. xUnit didn't work with build because NuGet restore was called too late. It should be called before running MSBuild on solution. Detailed description can be found on the Nuget Documentation website. After applying that solution it just works without installing VS or any other 3rd...
.net,visual-studio-2013,msbuild,nuget,nuget-package-restore
I would keep the NuGet.Config file since you are using it to change the default packages directory. You can delete the NuGet.exe and NuGet.targets file from the .nuget directory and remove the Import in your project files that refers to NuGet.targets....
c#,asp.net,nuget,visual-studio-2015,nuget-package-restore
For some reason, it took far too long to find this document on Migrating MSBuild-Integrated solutions to Automatic Package Restore but I was able to resolve the issue I was experiencing using the methods described here. Basically, you remove the '.nuget' solution directory along from the solution and then remove...
c#,nuget,build-process,nuget-package-restore
Try nuget restore solutionABC.sln See https://docs.nuget.org/consume/command-line-reference See bolded section below as to why you get the error. Restore Command Notes The restore command is executed in the following steps: Determine the operation mode of the restore command. If packages.config file is specified, nuget restores packages listed in the packages.config file....
nuget,travis-ci,nuget-package-restore
It is a problem with the Microsoft.ApplicationInsights NuGet package. In its .nuspec file it has the following: <metadata minClientVersion="2.8.50313"> NuGet will check the minClientVersion defined by a NuGet package against its product version to see if they are compatible. The minClientVersion used in the Microsoft.ApplicationInsights NuGet package seems to be...
Package Restore is NOT the same as installing a package. What you are seeing is by design. It simply downloads any missing packages in the packages folder. No more. No less. Package Restore was added so you wouldn't need to commit the packages folder to source control. It is expected...
msbuild,nuget,win-universal-app,c++-cx,nuget-package-restore
Place following config file next to nuget.exe nuget.exe.config <?xml version="1.0" encoding="utf-8"?> <configuration> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Microsoft.Build" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="12.0.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.Build.Engine"...
visual-studio-2013,nuget,tfsbuild,tfs2013,nuget-package-restore
I believe the Automatic Package Restore hooks into the Build Solution event. Since there's no solution, it's not triggering the restore. To build a single project, you may need to create a new solution that references just that project....
c#,nuget,nuget-package,nuget-package-restore
NuGet currently has some service issues related to search and package restore functionality. It is possible this is the cause of your package restore failure. If other dev machines are working OK, it's likely they have access to a cached version of this package. ...
visual-studio,github,nuget-package-restore
Okay, so grabbed the project from GitHub and attempted to build (but failed as you did). Your build status in your README is saying it can't get a build up either. Did some digging though, it appears your FoosballOld.csproj has a lot of broken references (based on its location being...
visual-studio-2013,nuget,nuget-package-restore
Nuget is down right now, so this why you might this issue with your solution.
nuget,csproj,nuget-package-restore
As of Nuget.exe v2.8.3, there isn't any way to do a solution-wide restore and update (at least when not all the projects in a given folder hierarchy are part of a solution). We ended up using the workflow described in How do I update a single nuget package in a...
.net,tfs,nuget,tfsbuild,nuget-package-restore
Turns out it was a bug in NuGet, which is fixed in the VS2015 RC: Source: https://github.com/NuGet/Home/issues/504...
asp.net-mvc-4,nuget-package,nuget-package-restore
Install it manually using nuget package manager PM> Install-Package Microsoft.Data.Edm -Version 5.0.0.50403. I can just find this version here. The latest version seems to be EdmLib for OData v1-3 5.6.3. Mostly, the package manifest from your previous machine had 5.0.0 instead of 5.0.0.50403
msbuild,nuget,visual-studio-online,tfs2013,nuget-package-restore
This was a change in TFS 2013 Update 2 and is reflected in VS, TFS, and VSO...
What I ended up doing is using restore from with a relative path like so : nuget.exe restore ..\ ...
It turns out that the name packages.config is expected, but any other config file name is rejected. My solution was to put my bigpackages.config file in a subfolder, using the accepted filename. This command succeeds: Nuget.exe restore [path]\big\packages.config -PackagesDirectory [path]\build\packages ...
visual-studio,visual-studio-2012,nuget,nuget-package-restore
Finally it end up to the following simple scenario (unfortunately I cannot reproduce the issue): package in trouble where homemade package of boost library. some of these package may have been available with the same name, but different content and version numbering on nuget.org On a workstation having the issue...
nuget,nuget-package,nuget-package-restore,nuspec
Unfortunately nuget.exe spec doesn't work like that. It expects a package ID. If you need to create a nuspec in a given folder, you will need to change to that directory. pushd ..\MYDEMOFOLDER // switch to new directory (remember current) nuget spec MYPROJECT // create MYPROJECT.nuspec file nuget pack MYPROJECT.csproj...