I don't like the glib dismissal of dependency management. Whilst breaking dependecy on CLR system dlls is a bit pointless, inter-project dependenies are bad news because they prevent the sort of reuse I first mentioned above. If you have projects A and B, then it's better OO design to make a new project AB that absorbs the binding than it is to create a cyclic dependence between A and B (otherwise there is little point having them separate). If the point then is demoted to "badly designed code is bad", well duh, I can't easily disagree. Otherwise, the scheme of having multiple orthogonal, non-monolithic, reusable sub-projects in a solution makes some sense to me.
Add a comment...