Is there any difference about namespace between VB.NET and C#.

[ad]

Is there any difference about namespace between VB.NET and C#.

All functions in c# must include in a namespace.

Why I can't find namespace in the files .vb .

How VB.NET implement the concept of namespace

[Peter Rilling]

I believe there is a "global" or "default" namespace in the CRL. I might be
wrong, but I think VB.NET allows classes to be part of this default
namespace while c# requires all classes to be part of a namespace.

"ad" <[e-mail]> wrote in message
news:#U**************@TK2MSFTNGP12.phx.gbl...

Is there any difference about namespace between VB.NET and C#.

All functions in c# must include in a namespace.

Why I can't find namespace in the files .vb .

How VB.NET implement the concept of namespace

[Daniel O'Connell [C# MVP]]

"Peter Rilling" <pe***@nospam.rilling.net> wrote in message
news:e6*************@TK2MSFTNGP10.phx.gbl...

I believe there is a "global" or "default" namespace in the CRL. I might
be
wrong, but I think VB.NET allows classes to be part of this default
namespace while c# requires all classes to be part of a namespace.

C# does not require anything be contained in a namespace, the default file
just happens to provide one.

[Samuel R. Neff]

Also, VB.NET provides a default namespace for the project and this
becomes prepended to the namespace to form the CLR namespace.

So, if you have a project with default namespace "Blinex.Charts" and
then a class:

Namespace Assets
Class LimitLine
End Class
End Namespace

Then the namespace in the CLR for referring to that class is
Blinex.Charts.Assets.LimitLine.

So in VB.NET even when you have no Namespace statement, classes are
still in a namespace defined by the project.

In contrast, the C# default namespace just defines the default value
put in the *.cs file. The *.cs file totally determines the actual
namespace though and it can be changed for each file.

HTH,

Sam
On Fri, 18 Mar 2005 17:29:26 -0600, "Daniel O'Connell [C# MVP]"
<[e-mail]> wrote:

"Peter Rilling" <pe***@nospam.rilling.net> wrote in message
news:e6*************@TK2MSFTNGP10.phx.gbl...

I believe there is a "global" or "default" namespace in the CRL. I might
be
wrong, but I think VB.NET allows classes to be part of this default
namespace while c# requires all classes to be part of a namespace.

C# does not require anything be contained in a namespace, the default file
just happens to provide one.

B-Line is now hiring one Washington D.C. area VB.NET
developer for WinForms + WebServices position.
Seaking mid to senior level developer. For
information or to apply e-mail resume to
sam_blinex_com.

[Daniel O'Connell [C# MVP]]

"Samuel R. Neff" <bl****@newsgroup.nospam> wrote in message
news:km********************************@4ax.com...

Also, VB.NET provides a default namespace for the project and this
becomes prepended to the namespace to form the CLR namespace.

So, if you have a project with default namespace "Blinex.Charts" and
then a class:

Namespace Assets
Class LimitLine
End Class
End Namespace

Then the namespace in the CLR for referring to that class is
Blinex.Charts.Assets.LimitLine.

So in VB.NET even when you have no Namespace statement, classes are
still in a namespace defined by the project.

In contrast, the C# default namespace just defines the default value
put in the *.cs file. The *.cs file totally determines the actual
namespace though and it can be changed for each file.

I thought it was something like that, but I don't know anywhere enough about
VB to have answered. Thanks for the info.