[eluser]Rick Jolly[/eluser]
[quote author="beemr" date="1219278840"]
I might just follow your suggestion and try making a "user" library that contains "model"-type behavior for all of the models that actually make up a full "User".
[/quote]
The more I think about it, the less sense the library approach makes. Unless the library is generic enough to use with all models, it can't be reused so it doesn't fit my definition of a library. Maybe this is just semantics, but if you're dealing with data, use models. To organize and breakup your user model code, you could go with composition or inheritance. I prefer inheritance.
[quote author="beemr" date="1219278840"]
So, what are the big frameworks behind domain design? It's my understanding that .NET is trying to release its own MVC pattern. Are they giving up on domain-based design?[/quote]
What does that has to do with "domain specific design"?
