Why you don’t need more projects

by Sep 29, 2022

After 15 years of taking over other .NET developer their solutions, one thing that always flabbergasts me is…

All the reasons why they have created dozens of projects in their solution.

I even, once in a while, come across a 100+ projects in 1 solution in the wild that tries to bring down Visual Studio in its path.

I see even amazingly simple applications, like a console utility, producing multiple libraries for no good reason.

But why?

❌ We want to prevent developers from mixing layers. It provides a separation by concern driven by the compiler.

❌ We don’t mix interfaces with concrete types. This makes reusing the interfaces very easy.

❌ Each namespace needs to have its own project. This is easier to see where code lives.

Projects are for modularization, for package management: it’s a component that you share with the world and/or need to deploy.

Principles I use when to create a new project:

✅ Release Equivalence Principle (REP)
Code that makes sense that you release and version together. What if you would make a NuGet package and versioning it? People that would use it would be dependent on the releases and look closely at the versions to keep track of it.

Common Reuse Principle (CRP)
Code that you reuse most of the time together, should be together. If you reference the library, would that be enough, or are you forced to reference other libraries? If yes, you are probably better off merging them.

Common Closure Principle (CCP)
If a normal change affects a certain code, then that code should probably be together.

Most of the time, you just keep the urge to create a new project for yourself and wait until you feel friction. That friction should be a hint to look if adding a project would solve the situation.

Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

I’m dropping GitVersion.

I'm dropping GitVersion. After working with GitVersion for a while, I decided to simplify things. GitVersion is powerful, but it often felt like overkill for my projects. I wanted something that followed SemVer, didn't require complex configuration, and "just worked"...

read more

JetBrains Rider is free!

JetBrains Rider is free! At least for Non-Commercial use. My favorite IDE is free. This is so cool! I hope this will help more people to start with C# development. We have Visual Studio Community but that only works on Windows. Now we have an IDE that works on all...

read more