Friday, December 18, 2015

Adding alternative NuGet package source in Visual Studio solution

While it's possible to add a new package source to Visual Studio this is not optimal if there are more than one developer or if a build server is used.

An alternative is to add a .nuget folder and within that folder add a NuGet.config file with the following content:

<?xml version="1.0" encoding="utf-8"?>
      <add key="NuGet official package source" value="" />
      <add key="Some other package source" value="some url to the other package source" />
   <disabledPackageSources />
      <!-- this tells that all of them are active -->
      <add key="All" value="(Aggregate source)" />


1 comment:

Unknown said...

I can also add that if some dll file was lost, for some reason, you may upload it with vcruntime140.dll download. This website can come up with all errors. Just because of that, it keeps a lot of useful dll files for PC. Please take this advice, if you suddenly will need a help.