nuget-package-restore

Is the Host Controller on Visual Studio Online now automatically restoring NuGet package before calling MSBuild? Previously I had to manually execute the following: nuget.exe restore MySolution.sln Now, when creating a new build in a new project, I noticed that I didn't need to do this. When looking at the build logs, I see this: This was a change in TFS 2013 Update 2 and is reflected in VS, TFS, and VSO... 来源： https://stackoverflow.com/questions/30037083/visualstudioonline-nuget-restore-now-built-in

We are experiencing some weird behavior using Jenkins and MSBuild. When manually typing into a command line to build a build.xml project: msbuild build.xml /T:Package /P:PublishProfile=Test /P:Platform="AnyCPU" /P:VisualStudioVersion=12.0 The build process works exactly as expected (build, packaging, etc.) However, if I am using Jenkins to do exactly this - that is - open a command line and run this exact command, I get an error saying: The command ""..\.nuget\NuGet.exe" install "C:\Jenkins\jobs\.....\workspace\MYPROJECT\packages.config" -source "" -NonInteractive -RequireConsent -solutionDir

I've recently switched to NuGet's latest recommended method which is using a `packages.json' file for projects: { "dependencies": { "Newtonsoft.Json": "9.0.1", "RestSharpSigned": "105.2.3" }, "frameworks": { "net45": {} }, "runtimes": { "win": {} } } This works great in my local visual studio environment, but the CI server can no longer build the project. What's odd is that I can see the packages being successfully restored for the solution, but on build, MSBuild has no idea where those DLLs are and all references to them fail: Package Restore Succeeding: 09:48:07 Updating NuGet.exe to 3.4.4

I have a mixed environment where some developers are working on Visual Studio 2013, and others are working on 2015. Everything worked fine until we updated a referenced NuGet package from Visual Studio 2015. Now, when trying to restore the NuGet packages from Visual Studio 2013, I see the following error: NuGet Package restore failed for project Foo: The 'System.Linq 4.0.0' package requires NuGet client version '3.0' or above, but the current NuGet version is '2.8.60723.765'.. Apparently, there is no NuGet version 3.x for Visual Studio 2013. Is there a solution to continue working with both

Is there any way in the Nuget.Config to default the Package Management option to "PackageReference"? I'm going to assume no since I didn't see it here but I thought I'd ask. I'm looking to default this on all developer machines for a certain repository and I was hoping I could change this in the Nuget.Config file that is stored in source control. This is what I'm talking about: In Visual Studio 2017 you can define the settings in a NuGet.Config file. <configuration> <packageManagement> <add key="format" value="1" /> <add key="disabled" value="False" /> </packageManagement> </configuration> The

We are developing multiple solutions in Visual Studio 2015. The solutions share some core projects that need nuget packages. The nuget references cannot be resolved when the nuget package is added from one solution and is later opened by another solution. The folder structure is as follows: Codebase SharedProjects SharedProject1 SolutionA WebProjectA packages folder A SolutionB WebProjectB packages folder B When I install a nuget package to SharedProject1 when SolutionA is opened, the dll reference shows the path to the packages folder A . When SolutionB is opened in another computer,