Don,

>Thanks for the info. I was contemplating all of the presentation and business logic for a given module to be in that module. Using my analogy to an accounting app, everything needed to run AR is in the AR module. I think you are recommending maintaining all of the BO for all modules in the Main module. Right?

I recommend putting them in a single business object project if they are used from all modules. If they are only used in a particular module you can choose to break them out into a separate business object project. Also, keep in mind there is a slight performance hit as you begin to increase the number of separate assemblies that are a part of your project. For more information, check out the MM .NET Dev Guide "Recommended Reading" section for the book "Improving .NET Application Performance and Scalability".

Best Regards,