>>>>>Hi,
>>>>>I would like to ask for opinion should I have ALL business object (each link to single table) into single project?
>>>>>I am facing problem that, some BOs are in difference project and link to difference table in difference database, but they need to refer to each other.
>>>>>
>>>>>How could I "categorize" them?
>>>>
>>>>I don't know if this helps, but here is my usual namespace/project structure for anything more than a small utility app:
>>>>
>>>>

>>>><CompanyName>.<SubsetName>.<FunctionalityName>.<ProjectName>
>>>>
>>>>Everything in a subset is usually in the same solution.
>>>>
>>>>Here is my project structure:
>>>>MyCompany.Dealer.WebUI.DealerOnline
>>>>MyCompany.Dealer.ConsoleUI.DealerDataLoad
>>>>MyCompany.Dealer.WindowsUI.DealerAdministrativeSystem
>>>>MyCompany.Dealer.BusinessLogic
>>>>MyCompany.Dealer.DataAccess
>>>>MyCompany.Dealer.Common
>>>>

>>>>
>>>>I put all of my business objects in my Common project as they will be accessed through all projects in the Dealer subset. All of my projects are named with their full namespace included (which causes some problems with newer version of Visual Studio because there is a size limit to the length of project filenames).
>>>
>>>You mean there is now a name length limit which didn't use to exist? That's pretty goofy.
>>>
>>>Thanks for posting that hierarchy. Good food for thought.
>>>
>>>PS -- Dealer? Who are the clients of your application, anyway? LOL
>>
>>We have customers, dealers, etc. We offer traditional loans to customers, but we also have a dealer servicing product line (think BillMeLater for the agricultural sector - coops, seed corn dealers, fertilizer dealers,etc.).
>
>It was just a joke. I didn't really think your clients are drug dealers.

Haha, I didn't catch that. Naw, if drug dealers were my clients I would move to where they were more prevalent - like SEC country.