Hi Mikhail,

Basically VS 2002/2003 taught us to use namespaces. This made sense
especially when building a web site with say multiple Default.aspx pages in
different folders such as admin, account, products...essentially an
organizational management tool. In a products folder the customer uses
CustomerCart.aspx to see their items but in the Admin folder I am looking at
the customer cart and it has quit a bit of different functions that the
customer is not privy to...same class, different folder, hence use a
namespace. VS 2002/2003 had it all set up with the DefaultNamespace property
and pages generated in different folders automatically generated namespaces
for those folders. This is also true with controls defined in different
parts of the sites I develop.

Since VS 2005 now has no namespace there is no automatic management help for
this type of class segregation which is the whole idea of namespaces in the
first place....except for the convoluted class names that are now generated.
Appears as though the automatic dynamic generation of the auto portion of
the partial classes was traded for the convoluted naming. Not what I as a
developer am expecting and it is not something I want either. When the
wizard asks me for a new web form name I expect the class name to match. Now
it does not.

It would really be helpful if I could get the three questions answered that
I already posed. That is because at this point doing a conversion from VS
2002/2003 is not obvious nor easy.

Thanks,
Gery

Gery D. Dorazio
Development Engineer
EnQue Corp.
phone: 704.377.3327
email : gdorazio@enque.net
web : www.EnQue.net