Be consistant with it, too. I have caught myself using a different namespace structure in different solutions. For now when I work on a new solution, I keep my old solution open so I can refer back to the previous structure that I used.

>Thank you, Bonnie. It is clear now. I have to now come up with a good naming convention of my namespaces so that it makes sense when I have to maintain the app.
>
>>Yes, right-click on the project in Solution Explorer ... that is what Einar meant.
>>
>>BTW, in addition to changing my Default namespace, I also change the Assembly name too (this will be the actual filename of the DLL).
>>
>>~~Bonnie
>>
>>
>>
>>>>It is a good practice to use the MyCompany.MyApplication.Business.MyBusinessClass. approach for your namespaces, but use an abreviation for your company name (because you will be typing it a lot <s>). I use "ALS" for my apps at work so that when I type "ALS." intellisense takes over.
>>>>
>>>>You can change each class you create manually but that would be a pain in the a$$. so the wonderful people at M$ added a way to set a default namespace for an assembly in VS. Just righ-click your assembly in the solution explorer and select properties. Then change the Default Namespace to DL.MyApp....whatever
>>>>
>>>>HTH,
>>>>Einar
>>>
>>>When you are saying click on he assembly, what is it? I can click on the Solution name and get properties but that does not have a default Namespace. When I right mouse click on a project and select properties, I can see default NameSpace. Is that what you mean by assembly?
>>>
>>>Thank you for your help.