Continuous Integration in VSTS I will demonstrate how to setup basic continuous integration to build, test and publish code every time someone commits changes to version control. Requirements VSTS account A VSTS git repository Setting Up Continuous Integration Go to your project in VSTS and follow the steps: Find the Files tab of the Code hub, and then click Set up build and confirm the VSTS repository and branch In the right panel, select .
How to host your own NuGet Packages There are mainly three different ways you can host your nuget packages privately: Local feed: Packages are placed on a network file share, ideally using nuget init and nuget add to create a hierarchical folder structure (NuGet 3.3+) NuGet.Server: Packages are made available through a local HTTP server NuGet Gallery: Packages are hosted on an Internet server using the NuGet Gallery Project Microsoft points to other several products that support remote private feeds.
What is Nuget? According with nuget.org, NuGet is the package manager for .NET. The NuGet client tools provide the ability to produce and consume packages. Packages means compiled code provided as DLLs files along with other content needed in the projects that consume these packages. Microsoft summarized the definition as “NuGet package is a single ZIP file with the .nupkg extension that contains compiled code (DLLs), other files related to that code, and a descriptive manifest that includes information like the package’s version number”.