LOL, I get your point, but that didn't answer my question. I will check out that book too.

>According to naming guidelines, none of them.
>
>YellowLabTechnologies.Customer.BusinessLogic or YellowLabTechnologes.BusinessLogic.Customer
>
>You should explicitly name everything.
>
>It's layed out in http://www.amazon.com/Framework-Design-Guidelines-Conventions-Development/dp/0321246756/ref=pd_bbs_sr_2?ie=UTF8&s=books&qid=1201551315&sr=8-2
>
>>I have a quick question about namespace naming standards:
>>
>>Let's say I have 3 separate systems: Customer, Dealer, and Employee. I want to separate the tier into logical namespaces.
>>
>>Which naming method is the best:
>>YLT.Customer.BLL
>>YLT.Dealer.BLL
>>YLT.Employee.BLL
>>YLT.Customer.DAL
>>YLT.Dealer.DAL
>>YLT.Employee.DAL
>>
>>or
>>
>>YLT.BLL.Customer
>>YLT.BLL.Dealer
>>YLT.BLL.Employee
>>YLT.DAL.Customer
>>YLT.DAL.Dealer
>>YLT.DAL.Employee