Namespaces - broad question

[Random]

I'm confused about the proper use and usefulness of namespaces. I beleive I
understand the purpose is so the developer can put classes within namespaces
to essentially organize your code. And I understand that you declare your
intention to use a namespace within a page through the "Inherits" attribute.
I know that using "Inherits" isn't absolutely necessary, it's just
recommended so the developer doesn't have to type out the entire namespace
in code. I know that namespaces have to appear in the project assembly,
however...

How does the assembly find a namespace that the developer has written????
In all the examples I've seen, namespaces have been written in codebehind
pages. How does this make them accessible to the entire project? What's to
prevent a duplicate namespace from being written in a different codebehind
page? Is there a better place to write all the project namespaces for more
centralized accessibility?

And finally, how do namespaces DIFFER from classes?

Random

[Marina]

First of all, namespaces can be used with the 'Imports' keyword, so as not
have to write out the full namespace for every class, not the 'Inherits'
attribute.

Think of namespaces as folders in your file system, and classes as the files
in them. So a namespace itself isn't anything but an organizational
container for classes - just as a folder is just a container for files.
Classes are the actual things that you instantiate, and call methods on.

I didn't really understand your questions. I think they all stem from not
understanding what a namespace actually is.

"Random" <ci*******@hotm ail.com> wrote in message
news:uD******** ******@TK2MSFTN GP10.phx.gbl...

I'm confused about the proper use and usefulness of namespaces. I beleive I understand the purpose is so the developer can put classes within namespaces to essentially organize your code. And I understand that you declare your
intention to use a namespace within a page through the "Inherits" attribute. I know that using "Inherits" isn't absolutely necessary, it's just
recommended so the developer doesn't have to type out the entire namespace
in code. I know that namespaces have to appear in the project assembly,
however...

How does the assembly find a namespace that the developer has written????
In all the examples I've seen, namespaces have been written in codebehind
pages. How does this make them accessible to the entire project? What's to prevent a duplicate namespace from being written in a different codebehind
page? Is there a better place to write all the project namespaces for more centralized accessibility?

And finally, how do namespaces DIFFER from classes?

Random

[Marina]

First of all, namespaces can be used with the 'Imports' keyword, so as not
have to write out the full namespace for every class, not the 'Inherits'
attribute.

Think of namespaces as folders in your file system, and classes as the files
in them. So a namespace itself isn't anything but an organizational
container for classes - just as a folder is just a container for files.
Classes are the actual things that you instantiate, and call methods on.

I didn't really understand your questions. I think they all stem from not
understanding what a namespace actually is.

"Random" <ci*******@hotm ail.com> wrote in message
news:uD******** ******@TK2MSFTN GP10.phx.gbl...

I'm confused about the proper use and usefulness of namespaces. I beleive I understand the purpose is so the developer can put classes within namespaces to essentially organize your code. And I understand that you declare your
intention to use a namespace within a page through the "Inherits" attribute. I know that using "Inherits" isn't absolutely necessary, it's just
recommended so the developer doesn't have to type out the entire namespace
in code. I know that namespaces have to appear in the project assembly,
however...

How does the assembly find a namespace that the developer has written????
In all the examples I've seen, namespaces have been written in codebehind
pages. How does this make them accessible to the entire project? What's to prevent a duplicate namespace from being written in a different codebehind
page? Is there a better place to write all the project namespaces for more centralized accessibility?

And finally, how do namespaces DIFFER from classes?

Random

[Random]

Hmm. I'm trying to teach myself from examples and tutorials and books.
Specifically in this case, I'm trying to learn from the MS PortalStarterKi t.
Specifically, the default page in that example has as the first line in
default.aspx:

<%@ Page CodeBehind="Def ault.aspx.vb" language="vb" AutoEventWireup ="false"
Inherits="ASPNE T.StarterKit.Po rtal.CDefault" %>

The codebehind page has:

Namespace ASPNET.StarterK it.Portal
Public Class CDefault
Inherits System.Web.UI.P age
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
<code here>
End Sub
End Class
End Namespace

I'm trying to find out how and why this works the way that it does. It's
more complex than the examples given by tutorials and books.

And again, I'm trying to figure out how the namespace declared here makes
it's way into the assembly. And because it does, somehow, does that make it
available through the entire project?

Random

"Marina" <so*****@nospam .com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

First of all, namespaces can be used with the 'Imports' keyword, so as not
have to write out the full namespace for every class, not the 'Inherits'
attribute.

Think of namespaces as folders in your file system, and classes as the files in them. So a namespace itself isn't anything but an organizational
container for classes - just as a folder is just a container for files.
Classes are the actual things that you instantiate, and call methods on.

I didn't really understand your questions. I think they all stem from not
understanding what a namespace actually is.

"Random" <ci*******@hotm ail.com> wrote in message
news:uD******** ******@TK2MSFTN GP10.phx.gbl...

I'm confused about the proper use and usefulness of namespaces. I beleive

I

understand the purpose is so the developer can put classes within namespaces

to essentially organize your code. And I understand that you declare

your intention to use a namespace within a page through the "Inherits"

attribute.

I know that using "Inherits" isn't absolutely necessary, it's just
recommended so the developer doesn't have to type out the entire namespace in code. I know that namespaces have to appear in the project assembly,
however...

How does the assembly find a namespace that the developer has written???? In all the examples I've seen, namespaces have been written in codebehind pages. How does this make them accessible to the entire project? What's to

prevent a duplicate namespace from being written in a different

codebehind page? Is there a better place to write all the project namespaces for

more

centralized accessibility?

And finally, how do namespaces DIFFER from classes?

Random

[Random]

Hmm. I'm trying to teach myself from examples and tutorials and books.
Specifically in this case, I'm trying to learn from the MS PortalStarterKi t.
Specifically, the default page in that example has as the first line in
default.aspx:

<%@ Page CodeBehind="Def ault.aspx.vb" language="vb" AutoEventWireup ="false"
Inherits="ASPNE T.StarterKit.Po rtal.CDefault" %>

The codebehind page has:

Namespace ASPNET.StarterK it.Portal
Public Class CDefault
Inherits System.Web.UI.P age
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
<code here>
End Sub
End Class
End Namespace

I'm trying to find out how and why this works the way that it does. It's
more complex than the examples given by tutorials and books.

And again, I'm trying to figure out how the namespace declared here makes
it's way into the assembly. And because it does, somehow, does that make it
available through the entire project?

Random

"Marina" <so*****@nospam .com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

First of all, namespaces can be used with the 'Imports' keyword, so as not
have to write out the full namespace for every class, not the 'Inherits'
attribute.

Think of namespaces as folders in your file system, and classes as the files in them. So a namespace itself isn't anything but an organizational
container for classes - just as a folder is just a container for files.
Classes are the actual things that you instantiate, and call methods on.

I didn't really understand your questions. I think they all stem from not
understanding what a namespace actually is.

"Random" <ci*******@hotm ail.com> wrote in message
news:uD******** ******@TK2MSFTN GP10.phx.gbl...

I'm confused about the proper use and usefulness of namespaces. I beleive

I

understand the purpose is so the developer can put classes within namespaces

to essentially organize your code. And I understand that you declare

your intention to use a namespace within a page through the "Inherits"

attribute.

I know that using "Inherits" isn't absolutely necessary, it's just
recommended so the developer doesn't have to type out the entire namespace in code. I know that namespaces have to appear in the project assembly,
however...

How does the assembly find a namespace that the developer has written???? In all the examples I've seen, namespaces have been written in codebehind pages. How does this make them accessible to the entire project? What's to

prevent a duplicate namespace from being written in a different

codebehind page? Is there a better place to write all the project namespaces for

more

centralized accessibility?

And finally, how do namespaces DIFFER from classes?

Random

[Marina]

This inherits attribute, refers to the name of the class this page inherits
from. The class's name is CDefault, but it is located in the
ASPNET.StarterK it.Portal namespace, and so the namespace has to preceed it.

At runtime, asp.net looks for a class with the name in the inherits
attribute.

This has nothing to do with projects, or namespaces being available. It is
just the fully qualified name of the class.

"Random" <ci*******@hotm ail.com> wrote in message
news:OI******** *****@TK2MSFTNG P09.phx.gbl...

Hmm. I'm trying to teach myself from examples and tutorials and books.
Specifically in this case, I'm trying to learn from the MS PortalStarterKi t. Specifically, the default page in that example has as the first line in
default.aspx:

<%@ Page CodeBehind="Def ault.aspx.vb" language="vb" AutoEventWireup ="false" Inherits="ASPNE T.StarterKit.Po rtal.CDefault" %>

The codebehind page has:

Namespace ASPNET.StarterK it.Portal
Public Class CDefault
Inherits System.Web.UI.P age
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
<code here>
End Sub
End Class
End Namespace

I'm trying to find out how and why this works the way that it does. It's
more complex than the examples given by tutorials and books.

And again, I'm trying to figure out how the namespace declared here makes
it's way into the assembly. And because it does, somehow, does that make it available through the entire project?

Random

"Marina" <so*****@nospam .com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

First of all, namespaces can be used with the 'Imports' keyword, so as not

have to write out the full namespace for every class, not the 'Inherits'
attribute.

Think of namespaces as folders in your file system, and classes as the

files

in them. So a namespace itself isn't anything but an organizational
container for classes - just as a folder is just a container for files.
Classes are the actual things that you instantiate, and call methods on.

I didn't really understand your questions. I think they all stem from not understanding what a namespace actually is.

"Random" <ci*******@hotm ail.com> wrote in message
news:uD******** ******@TK2MSFTN GP10.phx.gbl...

I'm confused about the proper use and usefulness of namespaces. I

beleive

I

understand the purpose is so the developer can put classes within

namespaces

to essentially organize your code. And I understand that you declare

your intention to use a namespace within a page through the "Inherits"

attribute.

I know that using "Inherits" isn't absolutely necessary, it's just
recommended so the developer doesn't have to type out the entire namespace in code. I know that namespaces have to appear in the project assembly, however...

How does the assembly find a namespace that the developer has written???? In all the examples I've seen, namespaces have been written in codebehind pages. How does this make them accessible to the entire project? What's

to

prevent a duplicate namespace from being written in a different

codebehind page? Is there a better place to write all the project namespaces for

more

centralized accessibility?

And finally, how do namespaces DIFFER from classes?

Random

[Marina]

This inherits attribute, refers to the name of the class this page inherits
from. The class's name is CDefault, but it is located in the
ASPNET.StarterK it.Portal namespace, and so the namespace has to preceed it.

At runtime, asp.net looks for a class with the name in the inherits
attribute.

This has nothing to do with projects, or namespaces being available. It is
just the fully qualified name of the class.

"Random" <ci*******@hotm ail.com> wrote in message
news:OI******** *****@TK2MSFTNG P09.phx.gbl...

Hmm. I'm trying to teach myself from examples and tutorials and books.
Specifically in this case, I'm trying to learn from the MS PortalStarterKi t. Specifically, the default page in that example has as the first line in
default.aspx:

<%@ Page CodeBehind="Def ault.aspx.vb" language="vb" AutoEventWireup ="false" Inherits="ASPNE T.StarterKit.Po rtal.CDefault" %>

The codebehind page has:

Namespace ASPNET.StarterK it.Portal
Public Class CDefault
Inherits System.Web.UI.P age
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
<code here>
End Sub
End Class
End Namespace

I'm trying to find out how and why this works the way that it does. It's
more complex than the examples given by tutorials and books.

And again, I'm trying to figure out how the namespace declared here makes
it's way into the assembly. And because it does, somehow, does that make it available through the entire project?

Random

"Marina" <so*****@nospam .com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

First of all, namespaces can be used with the 'Imports' keyword, so as not

have to write out the full namespace for every class, not the 'Inherits'
attribute.

Think of namespaces as folders in your file system, and classes as the

files

in them. So a namespace itself isn't anything but an organizational
container for classes - just as a folder is just a container for files.
Classes are the actual things that you instantiate, and call methods on.

I didn't really understand your questions. I think they all stem from not understanding what a namespace actually is.

"Random" <ci*******@hotm ail.com> wrote in message
news:uD******** ******@TK2MSFTN GP10.phx.gbl...

I'm confused about the proper use and usefulness of namespaces. I

beleive

I

understand the purpose is so the developer can put classes within

namespaces

to essentially organize your code. And I understand that you declare

your intention to use a namespace within a page through the "Inherits"

attribute.

I know that using "Inherits" isn't absolutely necessary, it's just
recommended so the developer doesn't have to type out the entire namespace in code. I know that namespaces have to appear in the project assembly, however...

How does the assembly find a namespace that the developer has written???? In all the examples I've seen, namespaces have been written in codebehind pages. How does this make them accessible to the entire project? What's

to

prevent a duplicate namespace from being written in a different

codebehind page? Is there a better place to write all the project namespaces for

more

centralized accessibility?

And finally, how do namespaces DIFFER from classes?

Random

[Random]

Okay, that clarifies the "Inherits" vs. "Imports" question very well.
Thanks.

As far as the namespace being available in the assembly, though, let me give
you an example...

Using the portal code I gave before, would I be able to write another aspx
page, use the same "Inherits=<full y qualified class name>" phrasing, without
that class being written into the different codebehind page referenced in
the new aspx page?

If yes, why? Shouldn't namespaces be written in a more centrally referenced
file?

If no, then how can the assembly keep track of all the declared namespaces?
And what would it do if two or more codebehind references had the same
namespace and class written in them?

Random

"Marina" <so*****@nospam .com> wrote in message
news:eq******** ******@TK2MSFTN GP10.phx.gbl...

This inherits attribute, refers to the name of the class this page inherits from. The class's name is CDefault, but it is located in the
ASPNET.StarterK it.Portal namespace, and so the namespace has to preceed it.
At runtime, asp.net looks for a class with the name in the inherits
attribute.

This has nothing to do with projects, or namespaces being available. It is
just the fully qualified name of the class.

"Random" <ci*******@hotm ail.com> wrote in message
news:OI******** *****@TK2MSFTNG P09.phx.gbl...

Hmm. I'm trying to teach myself from examples and tutorials and books.
Specifically in this case, I'm trying to learn from the MS PortalStarterKi t.

Specifically, the default page in that example has as the first line in
default.aspx:

<%@ Page CodeBehind="Def ault.aspx.vb" language="vb"

AutoEventWireup ="false"

Inherits="ASPNE T.StarterKit.Po rtal.CDefault" %>

The codebehind page has:

Namespace ASPNET.StarterK it.Portal
Public Class CDefault
Inherits System.Web.UI.P age
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
<code here>
End Sub
End Class
End Namespace

I'm trying to find out how and why this works the way that it does. It's

more complex than the examples given by tutorials and books.

And again, I'm trying to figure out how the namespace declared here makes it's way into the assembly. And because it does, somehow, does that make it

available through the entire project?

Random

"Marina" <so*****@nospam .com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

First of all, namespaces can be used with the 'Imports' keyword, so as

not have to write out the full namespace for every class, not the 'Inherits' attribute.

Think of namespaces as folders in your file system, and classes as the

files

in them. So a namespace itself isn't anything but an organizational
container for classes - just as a folder is just a container for files. Classes are the actual things that you instantiate, and call methods on.
I didn't really understand your questions. I think they all stem from not understanding what a namespace actually is.

"Random" <ci*******@hotm ail.com> wrote in message
news:uD******** ******@TK2MSFTN GP10.phx.gbl...
> I'm confused about the proper use and usefulness of namespaces. I

beleive

I
> understand the purpose is so the developer can put classes within
namespaces
> to essentially organize your code. And I understand that you declare your

> intention to use a namespace within a page through the "Inherits"
attribute.
> I know that using "Inherits" isn't absolutely necessary, it's just
> recommended so the developer doesn't have to type out the entire

namespace

> in code. I know that namespaces have to appear in the project assembly, > however...
>
> How does the assembly find a namespace that the developer has

written????

> In all the examples I've seen, namespaces have been written in

codebehind

> pages. How does this make them accessible to the entire project?

What's

to
> prevent a duplicate namespace from being written in a different

codebehind

> page? Is there a better place to write all the project namespaces

for more
> centralized accessibility?
>
> And finally, how do namespaces DIFFER from classes?
>
> Random
>
>

[Random]

Okay, that clarifies the "Inherits" vs. "Imports" question very well.
Thanks.

As far as the namespace being available in the assembly, though, let me give
you an example...

Using the portal code I gave before, would I be able to write another aspx
page, use the same "Inherits=<full y qualified class name>" phrasing, without
that class being written into the different codebehind page referenced in
the new aspx page?

If yes, why? Shouldn't namespaces be written in a more centrally referenced
file?

If no, then how can the assembly keep track of all the declared namespaces?
And what would it do if two or more codebehind references had the same
namespace and class written in them?

Random

"Marina" <so*****@nospam .com> wrote in message
news:eq******** ******@TK2MSFTN GP10.phx.gbl...

This inherits attribute, refers to the name of the class this page inherits from. The class's name is CDefault, but it is located in the
ASPNET.StarterK it.Portal namespace, and so the namespace has to preceed it.
At runtime, asp.net looks for a class with the name in the inherits
attribute.

This has nothing to do with projects, or namespaces being available. It is
just the fully qualified name of the class.

"Random" <ci*******@hotm ail.com> wrote in message
news:OI******** *****@TK2MSFTNG P09.phx.gbl...

Hmm. I'm trying to teach myself from examples and tutorials and books.
Specifically in this case, I'm trying to learn from the MS PortalStarterKi t.

Specifically, the default page in that example has as the first line in
default.aspx:

<%@ Page CodeBehind="Def ault.aspx.vb" language="vb"

AutoEventWireup ="false"

Inherits="ASPNE T.StarterKit.Po rtal.CDefault" %>

The codebehind page has:

Namespace ASPNET.StarterK it.Portal
Public Class CDefault
Inherits System.Web.UI.P age
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
<code here>
End Sub
End Class
End Namespace

I'm trying to find out how and why this works the way that it does. It's

more complex than the examples given by tutorials and books.

And again, I'm trying to figure out how the namespace declared here makes it's way into the assembly. And because it does, somehow, does that make it

available through the entire project?

Random

"Marina" <so*****@nospam .com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

First of all, namespaces can be used with the 'Imports' keyword, so as

not have to write out the full namespace for every class, not the 'Inherits' attribute.

Think of namespaces as folders in your file system, and classes as the

files

in them. So a namespace itself isn't anything but an organizational
container for classes - just as a folder is just a container for files. Classes are the actual things that you instantiate, and call methods on.
I didn't really understand your questions. I think they all stem from not understanding what a namespace actually is.

"Random" <ci*******@hotm ail.com> wrote in message
news:uD******** ******@TK2MSFTN GP10.phx.gbl...
> I'm confused about the proper use and usefulness of namespaces. I

beleive

I
> understand the purpose is so the developer can put classes within
namespaces
> to essentially organize your code. And I understand that you declare your

> intention to use a namespace within a page through the "Inherits"
attribute.
> I know that using "Inherits" isn't absolutely necessary, it's just
> recommended so the developer doesn't have to type out the entire

namespace

> in code. I know that namespaces have to appear in the project assembly, > however...
>
> How does the assembly find a namespace that the developer has

written????

> In all the examples I've seen, namespaces have been written in

codebehind

> pages. How does this make them accessible to the entire project?

What's

to
> prevent a duplicate namespace from being written in a different

codebehind

> page? Is there a better place to write all the project namespaces

for more
> centralized accessibility?
>
> And finally, how do namespaces DIFFER from classes?
>
> Random
>
>

[Marina]

I have no idea what you are talking about to be honest.

The class is already in a namespace - the Inherits attribute is just
referencing. It isn't creating a new namespace or a new class. So I have no
idea what you are talking about when you ask about namespaces being written
in central locations.

You can have any number of pages inherit from the same class - as long as
that class actually exists. In the visual studio model, you would have to
manually do that, because it assume a 1 to 1 ration between pages and code
behind classes.

If you tried to compiled two classes with the same name into the same
assembly, the compiler would not allow you to do this. The assembly itself
knows what classes it has, and what namespace each one is in, in it's
manifest.

I would recommend you start at the very basics of ASP.NET, it sounds like
you are missing some basic concept about how this all works. In your first
post you asked about the difference between a namespace and a class - so it
seems like you need to go to the beginning of .NET, and not just into the
middle of ASP.NET.

"Random" <ci*******@hotm ail.com> wrote in message
news:ua******** ******@TK2MSFTN GP09.phx.gbl...

Okay, that clarifies the "Inherits" vs. "Imports" question very well.
Thanks.

As far as the namespace being available in the assembly, though, let me give you an example...

Using the portal code I gave before, would I be able to write another aspx
page, use the same "Inherits=<full y qualified class name>" phrasing, without that class being written into the different codebehind page referenced in
the new aspx page?

If yes, why? Shouldn't namespaces be written in a more centrally referenced file?

If no, then how can the assembly keep track of all the declared namespaces? And what would it do if two or more codebehind references had the same
namespace and class written in them?

Random

"Marina" <so*****@nospam .com> wrote in message
news:eq******** ******@TK2MSFTN GP10.phx.gbl...

This inherits attribute, refers to the name of the class this page

inherits

from. The class's name is CDefault, but it is located in the
ASPNET.StarterK it.Portal namespace, and so the namespace has to preceed

it.

At runtime, asp.net looks for a class with the name in the inherits
attribute.

This has nothing to do with projects, or namespaces being available. It is

just the fully qualified name of the class.

"Random" <ci*******@hotm ail.com> wrote in message
news:OI******** *****@TK2MSFTNG P09.phx.gbl...

Hmm. I'm trying to teach myself from examples and tutorials and books. Specifically in this case, I'm trying to learn from the MS

PortalStarterKi t.

Specifically, the default page in that example has as the first line in default.aspx:

<%@ Page CodeBehind="Def ault.aspx.vb" language="vb"

AutoEventWireup ="false"

Inherits="ASPNE T.StarterKit.Po rtal.CDefault" %>

The codebehind page has:

Namespace ASPNET.StarterK it.Portal
Public Class CDefault
Inherits System.Web.UI.P age
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArg s) Handles MyBase.Load
<code here>
End Sub
End Class
End Namespace

I'm trying to find out how and why this works the way that it does. It's more complex than the examples given by tutorials and books.

And again, I'm trying to figure out how the namespace declared here makes it's way into the assembly. And because it does, somehow, does that make

it

available through the entire project?

Random

"Marina" <so*****@nospam .com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..
> First of all, namespaces can be used with the 'Imports' keyword, so as not

> have to write out the full namespace for every class, not the 'Inherits' > attribute.
>
> Think of namespaces as folders in your file system, and classes as

the files
> in them. So a namespace itself isn't anything but an organizational
> container for classes - just as a folder is just a container for

files. > Classes are the actual things that you instantiate, and call methods on. >
> I didn't really understand your questions. I think they all stem

from not

> understanding what a namespace actually is.
>
> "Random" <ci*******@hotm ail.com> wrote in message
> news:uD******** ******@TK2MSFTN GP10.phx.gbl...
> > I'm confused about the proper use and usefulness of namespaces. I
beleive
> I
> > understand the purpose is so the developer can put classes within
> namespaces
> > to essentially organize your code. And I understand that you

declare your
> > intention to use a namespace within a page through the "Inherits"
> attribute.
> > I know that using "Inherits" isn't absolutely necessary, it's just
> > recommended so the developer doesn't have to type out the entire
namespace
> > in code. I know that namespaces have to appear in the project

assembly,

> > however...
> >
> > How does the assembly find a namespace that the developer has
written????
> > In all the examples I've seen, namespaces have been written in
codebehind
> > pages. How does this make them accessible to the entire project?
What's
> to
> > prevent a duplicate namespace from being written in a different
codebehind
> > page? Is there a better place to write all the project namespaces for > more
> > centralized accessibility?
> >
> > And finally, how do namespaces DIFFER from classes?
> >
> > Random
> >
> >
>
>