Guidelines/principles for package and component design [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

开发者_C百科

We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.

Closed 6 years ago.

Improve this question

Alright, our visual studio solution grows big in terms of the number of projects in it. Except for things that are obvious, I want to check whether the way it is now is what it has to be or we can better reorganize/package it.

Do you know of any good text on guidelines, principles of package and component design that I can reference? Something in depth, with good analysis, not just tier a, b,c or layer 1, 2, 3, etc.

Thanks.

---

Chapter 28 in the book Agile Principles, Patterns, and Practices in C# by Robert Martin and Micah Martin covers the principles.