>Michael..
>
>I don't need to explicity import the system namespace or define the namespace with VB. But, assuming I had to, with VB, I still don't have to get caught up with case sensitivity, semi colons, and curly braces.
>

You only have to import classes that you intend to use with C#, same as with VB. If you intend to use a class you must import it.

You don't have to define a namespace with C# as well.

public Class Class1 {}

Case sensitivity does not bother me anymore, its something you get use to. With Intellisense it really minimizes the impact of remembering how classes and properties are defined and what you must type.

As far as semi colons, you have to have a command line terminator. I personally prefer using a semi colon verses a carriage return. It makes line continuation easier than having to use VB's underscore plus you can have multiple commands per line without having to use a colon <g>.

I also like using curly braces. It helps organize the code structure and separate the conditional logic. Maybe I just don't like having to type in a lot of end-this and end-that. I do understand your point of view on this coming from a VB background. The majority of people with a background in C and Java will not agree with you on this.

Don't get me wrong, I am well versed in VB and I do like the language. I also have considerable experience coding in C#. I just don't see any advantage using VB over C#. It is simply a personal choice. For new coding I will choose to use C#, however; I will create custom classes in VB.NET when porting from existing VB code. I see no reason to spend time re-writing code in C# when porting to VB.NET is so easy.