A useful principle in computer programming is DRY (Don’t Repeat Yourself). I am trying to follow this rule as I am refactoring a large .NET Framework MVC project by breaking it down into separate solutions.

One problem that I am still unable to resolve to my satisfaction involves a set of C# libraries (static functions, Authorization Attribute overrides, and others) that need to be identical in each solution. These solutions are pushed to TFS source control, which means that linked projects outside the solution will not copy to source control. In other words, all projects need to be contained within the solution.

This image is a (highly simplified) illustration of what I am trying to describe. My intention is for the top solution "C# .NET Framework Solution" to have the "master copy". The other solutions rely on those same libraries. While I can "link" to those solutions, that approach only works on the PC where those solutions are authored. Projects linked to outside the solution cannot be pushed (in my experience) to source control.

enter image description here

The approach I am using – which does work as intended – is to maintain my “master copy” of C# class libraries in a specific solution. I have manually copied the specific C# class library projects to each of the solutions that need them. The good thing is that because the “copied” project exists in the solution, the solution can be pushed to source control in the intended manner. The bad thing is that this is a “copy”.

My one question is this: is there a way to have the best of both worlds, where the C# library project exists in the solution, but if I make a change to the “master copy” all the “copies” in the other solutions are synced? Why would I want this? Imagine if the code does change in one or more of those libraries and I (or my successor) forgets to make those changes in all those other solutions? What if I make a mistake in one or more of the copies?

Is my current technique the only option I have, or is there a different way for me not to break the DRY principle?

2 Answers 2


Shortest answer ever : publish reusable library with required dependencies as NuGet package and install it wherever you need. It will help you in versioning as well.

If your class library is .NET Framework, converting it to .NET Standard will solve many problems involved with publishing it as a NuGet package. Visual Studio 2017 makes it very easy to do this, but only if it is .NET Standard.

To serve the NuGet packages, there are some options:

  • Copy the .nupkg file to a shared folder location. In Visual Studio, you can configure NuGet to read from that folder location Tools > Options > NuGet Packge Manager > Package Sources.
  • Follow the instructions on Hosting your own NuGet feeds.
  • I hadn't considered that, because my solutions need to be intranet-only. But according to this "stackoverflow.com/questions/14527615/…" it is possible. Commented Mar 13, 2018 at 17:26
  • yes, you can publish it to local nuget server. Commented Mar 13, 2018 at 17:28
  • 3
    @RahulAgarwal, you don't need a nuget server. Just put it on a network share and add the path to the share to your nuget config and it'll work just fine.
    – David Arno
    Commented Mar 13, 2018 at 17:47

If you're not into using NuGet, create a common utilities DLL and put it in a shareable folder. For example, we have a DBUtils.dll library of commonly used DB methods that we can add as a reference. It works great for us.

  • Have you tried that with source control? (E.g., Github, TFS) Commented Mar 13, 2018 at 17:27
  • Yeah. We use TFS. The share is it's own solution. We just reference the built DLL. Commented Mar 13, 2018 at 17:28
  • i don't think that will work well for bigger applications. Commented Mar 13, 2018 at 17:31
  • 4
    This is an acceptable method. The source code is still in source control. The binaries are not. As long as you build the solutions/projects in the right order, it is fine. Nuget is probably not as reliable. Commented Mar 15, 2018 at 1:29
  • 1
    We use this method for a 2mi LOC project and it work wonders.
    – T. Sar
    Commented Mar 15, 2018 at 19:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.