if asp.net 2.0 web site, the page file and the code behind are compiled
into one dll (they are actually treated as one source via partial
classes). as the code behind is the same "source" as the page there is
no need for a namespace. in a web site project aspnet_compiler compiles
all the code.
if you make a web project (I don't care for them), vs2005 compiles the
code behind in a dll it places in the bin folder, and then has the
aspnet_compiler to compile the pages. so if you specify a project
namespace, it still only on the code behind files (which now use
inhertance instead if partial classes).
not actully sure why you want a namespace on web pages, as they are
standalone units. normally you create shared code as a seperate library
project, where you would use a namespace.
note: in the web.config, you can specify default namespaces to include
in pages via the <namespaces> config section.
-- bruce (sqlwork.com)