Shared configuration of local nuget server

Apr 3, 2012 at 10:13 AM


We want to setup a local inhouse nuget server to protect us from "nuget is down" and also a possibility to add local packages. The problem we encounter is the configuration of this extra server. Is there any way to avoid configure every client (both build machines and developer's desktops)?

Our idea was to use our committed nuget.targets file for this (we use nuget 1.6 feature "enable nuget package restore"), but AFAIK this is not possible due to bug

Shortly put... Can we somehow centrally add this extra nuget server to all clients?



Apr 3, 2012 at 5:36 PM

You should be able to specify your sources in the target file. It's not going to keep it in sync with the sources you've configured, but replicating it in the two places should be a reasonable work around until we address the work item.

Apr 3, 2012 at 7:59 PM

My problem wasn't really about replication but to get the sources defined in nuget.targets being read at all (I obiviously misunderstand what the issue 1861 was all about). Sorry for being vague in my question.

However - after posting my question I found this,, which solved my problem.