nuget-package-restore

I have couple of build definitions that are using the "old" NuGet Installer task to restore the dependencies from our internal TFS feed (same collection); the feed url is specified through the NuGet source parameter: The restore process is working fine as below: Switching to the newer version of the task is causing the build failure: How can I disable the connection attempt to 93.184.221.200:443 due to the fact that the build agent doesn't have internet access? I'm using TFS 15.117.26714.0. Update 1 I copied nuget.exe to c:\nuget folder then added the folder to the PATH environment variable.

I am unable to install/restore nuget packages from a Visual Studio Team Services feed in an asp.net core web application (RC2). I receive the following: error: Response status code does not indicate success: 401 (Unauthorized). I am running Visual Studio Community 2015 Update 2 and nuget version 3.4.4. I am able to install/restore packages from this feed in other project types. Do I need to do something else to pass my credentials for an asp.net core web app? Steps to reproduce: From Team Services package tab I select "Connect to Feed" and copy the NuGet package source URL In visual studio ->

When I build my project from within VS2012 I get the following error message This project references NuGet package(s) that are missing on this computer. Enable NuGet Package Restore to download them. I have the nuget options set for NuGet to download missing packages. Yet I still get the error. I have nugget 2.7 installed. With VS2012 update 3 As Dan was alluding to, if your solution has a .nuget folder (from enabling package restore), then nuget 2.7's automatic package restore feature is disabled, as per http://docs.nuget.org/docs/workflows/migrating-to-automatic-package-restore . If

I've got TFS doing some continuous integration builds. Today, it broke for one solution. It seems it can't find AutoMapper. All the other packages can be found just fine. A couple relevant points: None of the packages are in source control, we're letting TFS restore them. We have an internal NuGet feed, but it doesn't seem to be a problem in other solutions, and in this solution we are still getting Entity Framework to restore - just not AutoMapper. I tried removing and re-adding the NuGet Packages. No luck. If I use Remote Desktop to connect to the build server and open the project in Visual

How it's possible that NuGet's Install-Package fails with Unable to find version 'x' of package 'y' when that exact version is released as NuGet to official repository and it shown on the https://www.nuget.org/packages/y page. Here is specific sample with nuget.org content and NuGet Install-Package command output. UPDATE. Package sources are set to defaults (from nuget.org). Actually you can see the issue just running Install-Package Log4Net.Async -Version 1.3.0 . UPDATE 2. I want to highlight that it's not about some developer's machine - the same things happening on Visual Studio Online

I am building a project to be installed as a NuGet package and I want to set the properties of a SpecFlow feature file (because it is latest SpecFlow and should not produce code-behind files for the features.) To achieve the effect of selecting a file, opening it's Properties pane and setting a couple of values, I have set my project structure like this: \MyProject \build MyProject.targets \Framework <the folder containing the file I want to affect> FrameworkTests.feature <the file I want to affect> \Framework FrameworkTests.feature <the original location of the file I want to affect> My