>>This project I am working on has classes nested inside of a class declaration and in most cases there are no namespaces declared. Needless to say I am strugling just to find stuff and to figure out accessability with the namespaces. Is this a typical way to organize VB.Net work?
>
>I would say that it is not typical but it isn't that bad neither.
>
>If you have classes that are nested, it is probably because it makes full sense that this insider class cannot be used as-is elsewhere.

Ah, well I guess I haven't run into a need to create dependancy with this method yet.
>
>As for the namespace, I know C# programmers who put the same namespace into all there application which does exactly the same as the default one provided by VB (which is not considered as a best practices).

Agreed, I am adding namespaces so I can logically seperate the way I need to.
Thanks for you comments Eric & Craig.
Tim