When you get the latest, how will you know that you're missing a dependency that NuGet should fulfill?

Let's say an error is like so:

Could not load file or assembly 'file:///C:\whatever\ui\bin\System.Net.Http.Formatting.dll' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

 
 

When you look at the reference to System.Net.Http.Formatting in the Solution Explorer does it have a path to a .dll like so:

• C:\whatever\packages\Microsoft.AspNet.WebApi.Client.5.2.2\lib\net45\System.Net.Http.Formatting.dll

...with "packages" in the mix? ...as opposed to a path like this for System.Net.Http:

• C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\System.Net.Http.dll

 
 

This should tell you that you need to run a Nuget command to put something in the packages folder such as:

Install-Package Microsoft.AspNet.WebApi.Client

 
 

You likely can find the command by just Googling against the name of the .dll and the word "NuGet" as that is how I found this.