>When working in a multi-developer environment with source control is it a good idea to have one concrete class per class lib. ( Think Meer Mortals where there are no SCXs all forms are in VCXs ) The Framework/Abstract classes are expected to continue to contain 1..N classes
>
>My gut says that there would be problems with this, but I cannot think of anything significant.
>
>Why it is being considered is that there should be much less conflict between developers needing to make changes to different classes in the same library. In a sense all that is being done is repeating the organizational ( or lack there of <s> ) structure of a project that uses SCX forms.

There isn't any major problems with this, beyond the fact that you end up with a lot more class libraries. Actually, the MM docs make the same suggestion (eg. breaking classes out for multi-dev use).

I'd put a bizobj in it's own class, along with it's business rules. I'd also consider putting the class's data environment in there as well so all the basic stuff you'd need while modifying a class is all together.