Why do I need NuGet Installer task

Why do I need the NuGet Installer task if there is an option on the Visual Studio Build task to Restore NuGet Packages?

The Restore NuGet Packages option of the Visual Studio Build task currently only searches NuGet.org for packages. If you are using a service like Visual Studio Team Service Package Management those feeds are not searched. 

By adding a NuGet.config file to your solution where the other feeds are defined using the NuGet Installer task will be able to restore packages from all your feeds. If you have already configured your package sources in Visual Studio. You can simply copy your NuGet.config file from %AppData%\NuGet and add it to your source control and use with the NuGet Installer task.

Comments (7) -

  • Derek Keeler

    12/18/2015 3:47:46 PM | Reply

    It is also required when you need to use a different version of nuget.exe (such as when a project you are working on requires the latest beta bits from the nuget team).

  • Srivatsa

    2/2/2016 5:48:04 AM | Reply

    I get these nuget errors very frequently when i  use the demo projects like MyShuttleBiz, MyHealthClinicBiz etc when i try to build .NET5 application. Any help from Donovan?

    • Donovan

      2/28/2016 1:33:12 AM | Reply

      Which errors are you getting?

      • DNU restore errors.

        2/29/2016 2:28:47 AM | Reply

        dnx runtime packages missing it says.

        • Donovan

          3/3/2016 5:46:21 AM | Reply

          I would wait for RC2 of ASP.NET 5 they are still changing a lot. But below is a link that might help. It might be a bit outdated but lays out how to deploy.


  • Rohit

    7/25/2017 9:55:42 AM | Reply

    I am using VSTS 2015. While building the solution , I have getting error of "This project references NuGet package(s) that are missing on this computer.. Use NuGet Package Restore to download them" .

    . What can be the alternative apart from   "NuGet Package restore" to resovle this issue?

    somewhere I read, we can create nuGet server, publish and deploy it in IIS, get its URL, and  mention the URL at "Nuget.config  ". Is it right way ? . If not, could you please help me in this issue

Add comment