You CAN do it that way, if you need to, but namespaces would not be the reason why. You may want to do it that way if, for instance, you want to re-use your custom controls or user controls across several solutions. I think it would be a good idea for that reason.

>I did use the wizard to create the App and Business Object projects. My question is on the third project I need to create so I can create my own visual objects, i.e.:
>
>public class myTextbox : mmTextbox
>{
>}
>
>I end up created another project called MyWindowsForms which contains all of my base form and base controls that I sub-classed from Mere Mortal. This will create a MyWindowsForms.dll for distribution.
>
>Stephen
>
>
>
>>Absolutely not. Start out simple and just create two projects, one for your UI (forms) and another for your business objects. This is how Kevin's wizard sets things up.
>
>>You can even have multiple namespaces in a single cs file, were you so inclined. There need not be any relationship to the directories.