- RT @mattyglesias: Look, just because Sessions hasn't actually been convicted of a crime is no reason we can't start seizing his property no… 8 hours ago
- Wow #DUNKIRK was pretty amazing. Go see it. 12 hours ago
- RT @FullFrontalSamB: “Sean Spicer crawled to freedom through five hundred yards of shit smelling foulness I can’t even imagine…” https://t.… 1 day ago
- RT @dotnetkicks: Creating a GitHub Issues Autoresponder using Webask.io by @NotMyself dotnetkicks.com/r/253540?url=h… #dotnet via @DotNetKicks 1 day ago
- RT @databozo: Doing a thing for school. If you have a kid and use(d) formula, mind taking a survey? surveymonkey.com/r/XHKFN6S 2 days ago
Configuring and Using an Internal NuGet Server
June 13, 2011Posted by on
This allows us to take advantage of the excellent .NET Open Source community, while keeping our “not for public” consumption libraries private. Our internal server hosts only our internal libraries and NuGet handles resolving all reference from the public package source. Which lends itself to a really clean workflow.
Next steps for us are to update to the latest version of TeamCity which has NuGet based build triggers.
Here is a quick video demonstrating how to use the internal/public feeds together from a users perspective in Visual Studio.