>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.

Good point... but that still leaves the issues of curly braces, case sensitivity, and semi colons...

>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.
>

Intellisense does help in some areas - I agree with you here. But when you have to define properties and the associated procedures, Intellisense does not help here...

Having to get "use to it" is a good way to put it...


>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>.
>

Multiple commands per line???? Why would you want to do that? As far as line continuation goes, VFP uses a semi colon. Whether it is a semi colon or a an underscore, it is still one charater - so I don't see the difference there. The thing I like about VB is that I don't have to explicitly define how a line is terminated.


>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.
>

I would expect people from C or Java to disagree with me here - just as I would expect people from VB or VFP to agree. The good news is that free choice exists. If I want to use VB - I can. If I want to use C# - I can. Regardless of the choice, I am not put at a technical disadvantage. Once the VB developer interacts with the .NET framework, going to C# won't be a big deal. The opposite case would hold true I am sure. IAC, if there is no reason to move if one does not have to or want to.

My point about VB is that for a number of reasons - I PREFER it. At no time have I tried to make a technical argument. Some however, try to make technical arguments to justify a choice. Perhaps some feel that by couching the reasons in technical terms, it somehow legitimizes the position. Put another way, perhaps some feel that if they simply stated "We use C# because we prefer it" is somehow not a valid reason for choosing the language. IMO, it is a legitimate reason for choosing a language and above all, it is not a pretense of a justification.

My concern is that if what are really perferential reasons are interpreted as technical reasons, people will be misled...

>
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.
<

I agree it is a personal choice.