>Hi John...
>
>You be the judge:

Yeah well, unfortunately that's a real bad misrepresentation.

First off you fail to include the namesspaces in your VB example which is required using the Imports keyword. Second the constructor in the C# is not required unless you actually use it.

What are you comparing here anyway? There are places (like an ASP.NET page for example) where C# doesn't require a namespace wrapper as well because the namespace is implied through the page. I presume that's why your VB example doesn't require a namespace qualifier. IAC, even if this is not required it's highly recommended that you do declare everything in a namespace explicitly so you can move things around later as you will surely have to do with class libraries you create for re-use later (unless you stick it the GAC).

+++ Rick ---


>
>C#
>
>

>
>using System;
>
>namespace CSharpClass
>{
>	public class Class1
>	{
>		public Class1()
>		{
>
>		}
>	}
>}
>
>

>
>Or VB
>
>

>
>Public Class VisualBasicClass
>
>End Class
>
>

>
>I understand this is a VERY simple comparison. Sometimes, the simple comparisions make for the best ones because they strip away extraneous items.
>
>All things being materially equal, I will forgo the archaic requirements of C#. How anybody can call C# "elegant" is beyond me....< s >...