Guidelines / principles for designing packages and components

Question

Well, our visual studio solution is growing in terms of the number of projects in it. Except for the obvious things, I want to check what it is now, or we can better reorganize / pack it.

Do you know any good text about the guidelines, design principles of packages and components that I can use? Something in depth, with good analysis, not just level a, b, c or layer 1, 2, 3, etc.

Thanks.

Answer 1

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