Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing NuGet with TFS across multiple development machines (DLLs not copied across)
    text
    copied!<blockquote> <p><strong>Possible Duplicate:</strong><br> <a href="https://stackoverflow.com/questions/8514640/using-nuget-to-share-code-across-developers">Using NuGet to share code across developers</a> </p> </blockquote> <p>I've recently swapped from managing library use by explicitly referencing 3rd party library DLLs that are stored in my projects in TFS in a 'libs' folder, to letting NuGet handle such project references. However, when I add a NuGet reference on one machine (for example to Daniel Crenna's <a href="http://github.com/danielcrenna/tweetsharp" rel="nofollow noreferrer">TweetSharp</a>) the DLLs do not seem to appear after fetching the latest version of the project on another machine. But NuGet thinks they are installed so I do not get the option of refreshing the installation.</p> <p>Perhaps this is easier to understand with some screenshots. (I'll include small ones with click-through to bigger.) </p> <p>Here's the project references added by NuGet on the original machine:</p> <p><a href="http://www.flickr.com/photos/dumbledad/6895612962" rel="nofollow noreferrer"><img src="https://farm8.staticflickr.com/7207/6895612962_b850e68a37_n.jpg" alt="Screenshot from original machine"></a></p> <p>and here is the corresponding screenshot from the second machine after fetching the latest version of the solution from TFS and rebuilding:</p> <p><a href="http://www.flickr.com/photos/dumbledad/6895653826" rel="nofollow noreferrer"><img src="https://farm8.staticflickr.com/7258/6895653826_887e26b786_n.jpg" alt="Screenshot from second machine"></a></p> <p>You'll see that the correct reference is in the project but it has the yellow warning triangle as the DLL is not available, but the NuGet dialog only offers "uninstall" not "install" nor "reinstall".</p> <p>How should I be using NuGet in conjunction with TFS across multiple development machines?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload