.NET Building Process - Github/Git and Dependent Projects

Question

I'm currently using Github/Git for two .NET solutions. The first solution is a library of common .NET code for all projects at my company, the second solution is a ASP.NET MVC Web Application.

What does a proper Nant or MSBuild file look like for cloning first repo, build it, clone second repo, add assemblies from first solution to the second? I plan on using Jenkins as my build server. I'm unclear of which parts are handled by the build server and which by the build file. I don't want to reinvent the wheel. Thanks.

Answer 1

You can have a build process set up for your company library that puts the compiled binaries into a shared location. For example a shared network drive, or (preferably) a private NuGet repository if you're using Visual Studio.

Then you add a reference to the assembly/NuGet package in your other projects. Personally, I'm a big fan of the NuGet route.

The benefit of using NuGet is that you don't have to use the new version as soon as it is released (although it is easy to upgrade).

Answer 2

use submodules to link the two. You will be able to clone recursively and have all that you need for your build to work.