Restoring Nuget References

Question

I have solution  amp  project in Visual Studio 2012    The project has a file packages config in the root of the project   For the purposes of this question  lets assume I accidentally removed these libraries from the References section of my project   When going into NuGet package manager  the interface is still reporting a tick next to these packages  indicating they are installed   The only way I can see how to fix this situation is to delete all the entries from packages config  which will fix the issue of the NuGet interface reporting them as installed  and re-add each one   Is there a smarter way  I had hoped enabling  enable nuget to restore missing packages  would solve this  but it doesnt seem to do anything

User · Answer

In case this helps someone  for me  none of the above was sufficient  I still couldn t build  VS still couldn t find the references  The key was simply to close and reopen the solution after restoring the packages  Here s the scenario  using Visual Studio 2012   You open a Solution that has missing packages  The references show that VS can t find them  There are many ways to restore the missing packages  including  building a solution that is set to auto-restore opening the Package Manager Console and clicking the nice  quot Restore quot  button doing nuget restore if you have the command line nuget installed  But no matter what the approach  those references will still be shown as missing  And when you build it will fail  Sigh  However if you close the solution and re-open it  now VS checks those nice  lt HintPath gt s again  finds that the packages are back where they belong  and all is well with the world  Update Is Visual Studio still not seeing that you have the package  Still showing a reference that it can t resolve  Make sure that the version of package you restored is exactly the same as the  lt HintPath gt  in your  csproj file  Even a minor bug fix number  e g  1 10 1 to 1 10 2  will cause the reference to fail  You can fix this either by directly editing your csproj xml  or else by removing the reference and making a new one pointing at the newly-restored version in the packages directory

User · Answer

I have to agree with  Juri that the vastly popular answer by jmfenoll is not complete  In the case of broken references  I submit that most of the time you do not want to update to the latest package  but only fix your references to the current versions that you happen to be using  And Juri provided a handy function Sync-References to do just that   But we can go just a bit further  allowing the flexibility to filter by project as well as package   function Sync-References  string  PackageId   string  ProjectName        get-project -all        Where-Object      name -match  ProjectName         ForEach-Object            proj                Write-Output   Project       proj name          Get-Package -project  proj name           Where-Object      id -match  PackageId             ForEach-Object                Write-Output   Package         id              uninstall-package -projectname  proj name -id    id -version    version -RemoveDependencies -force             install-package -projectname  proj name -id    id -version    version

User · Answer

Just in case it helps someone - In my scenario  I have some shared libraries  Which have their own TFS projects solutions  all combined into one solution   Nuget would restore projects successfully  but the DLL would be missing   The underlying issue was that  whilst your solution has its own packages folder and has restored them correctly to that folder  the project file  e g   csproj  is referencing a different project which may not have the package downloaded  Open the file in a text editor to see where your references are coming from   This can occur when managing packages on different interlinked shared solutions - since you probably want to make sure all DLLs are on the same level you might set this at the top level  This means it that sometimes it will be looking in a completely different solution for a referenced DLL and so if you don t have all projects solutions downloaded and up-to-date then you may get the above problem

User · Answer

Copy packages config file of project and applies all version modify Unistall all package and remove depencies   packages   Get-Package -ProjectName  nameOfProjectToRestore  foreach   package in  packages        uninstall-package  -projectname  nameOfProjectToRestore  -id  package Id -version  package version -RemoveDependencies -force      Clear the packages folder in the root of project Copy the modifies package config to root folder of website Run this code to restore the project   packages   Get-Package -ProjectName  nameOfProjectToRestore  foreach   package in  packages        uninstall-package  -projectname  nameOfProjectToRestore  -id  package Id -version  package version -RemoveDependencies -force     foreach   package in  packages        install-package   package Id -ProjectName  nameOfProjectToRestore  -Version  package Version

User · Answer

I had the same issue with missing references  Below my scenario    Fresh Windows 10 machine and VS Community 2015 install Just checked out repository code via TFS One solution built just fine  one solution had one project with missing references  EF  System Http  as instance   but the relative nuget packages were properly installed    All version numbers in project and packages match  doing nuget restore  in all its ways  did not work   How I fixed it  simply delete the package folders in the solution root and execute nuget restore  At this point the dlls are correctly downloaded and can be added for the missing references

User · Answer

The following script can be run in the Package Manger Console window  and will remove all packages from each project in your solution before reinstalling them   foreach   project in Get-Project -All          packages   Get-Package -ProjectName  project ProjectName     foreach   package in  packages            Uninstall-Package  package Id -Force -ProjectName  project ProjectName           foreach   package in  packages            Install-Package  package Id -ProjectName  project ProjectName -Version  package Version           This will run every package s install script again  which should restore the missing assembly references  Unfortunately  all the other stuff that install scripts can do -- like creating files and modifying configs -- will also happen again  You ll probably want to start with a clean working copy  and use your SCM tool to pick and choose what changes in your project to keep and which to ignore

User · Answer

You need to Enable NuGet package restore at the VS solution level for the restore missing package to work

User · Answer

In Visual Studio 2015  Soulution is under source control  MVC-Project   csano s Update-Package -Reinstall -ProjectName Your Project Name worked  but it messed up with some write locks    I had to delete the  packages -Folder manually before   It seemed to be locked because of the source control    Also  I had to re-install the MVC-Package from the NuGet Package Manager

User · Answer

I suffered from this issue too a lot  in my case Downloading missing NuGet was checked  but it is not restoring them  and i can not uninstall  amp  re-install because i modified some of the installed packages     so   I just cleared the cached and rebuild and it worked   Tools-Option-Nuget Package Manager - General   also this link helps https   docs nuget org consume package-restore migrating-to-automatic-package-restore

User · Answer

Try re-installing the packages   In the NuGet Package Manager Console enter the following command   Update-Package -Reinstall -ProjectName Your Project Name  If you want to re-install packages and restore references for the whole solution omit the -ProjectName parameter

User · Answer

This script will reinstall all packages of a project without messing up dependencies or installing dependencies that may have been intentianlyz removed    More for their part package developers    Update-Package -Reinstall -ProjectName Proteus Package LinkedContent -IgnoreDependencies

User · Answer

I added the DLLs manually  Right clicked on References in the project  select Add Reference and then in the dialog pressed the Browse button  The NuGet DLLs where in the packages directory of the solution  To get the names of them you can right click on references in another project that s working properly and select properties and look in the path property

User · Answer

While the solution provided by  jmfenoll works  it updates to the latest packages  In my case  having installed beta2  prerelease  it updated all of the libs to RC1  which had a bug   Thus the above solution does only half of the job   If you are in the same situation as I am and you would like to synchronize your project with the exact version of the NuGet packages you have or specified in your packages config  then  then this script might help you  Simply copy amp paste it into your Package Manager Console  function Sync-References  string  PackageId      get-project -all           proj            Write-Host  proj name       get-package -project  proj name          id -match  PackageId                Write-Host    id         uninstall-package -projectname  proj name -id    id -version    version -RemoveDependencies -force         install-package -projectname  proj name -id    id -version    version               And then execute it either with a sepific package name like  Sync-References AutoMapper   or for all packages like  Sync-References   Credits go to Dan Haywood and his blog post

[visual-studio-2012] Restoring Nuget References?

Update

Examples related to visual-studio-2012

Examples related to nuget