>John,
>
>Ok - here's the new thread per your request
>
>Re - my reasons for C# over VB .NET
>
>1 - C# is cleaner - doesn't carry the legacy baggage that VB does - in fact some of the same things that make VB "more like VFP" encumber it.

Exactly what bagage are your referring to?


>2 - My information is that C# runs about 10% faster in general (will actually ciomplile to MSIL more efficiently)

Is this really quantified or nothing more than anecdotal evidence? And, assuming it is true, is there a noticable difference between 10ms and 9ms? I understand that 10% can be a big number, but one needs to know more about the context. Further, one has to guage whether the 10% difference, assuming there is one, outweighs the productivity gains in VB.

Ken, if speed were always the decisive factor, everybody would program in C++.


>3 - .NET Framework is C#

And this translates into what advantage for you. A statement of fact yes, but as it stands now, it is a statement in the air. What demonstrable advantage is there for you?


>4 - since C# is very much like JAVA - we're learning two languages at once and will be prepared if the world turns upside down and the misguided open source freedom fighters take over the planet.

This is starting to sound more like Kevin's marketing material. Just because it looks like Java, does it really mean you could just leap to Java? 80% of what you do in dotNET involves the framework classes, and those will not be in Java.


>5 - And finally, if VB were the last language on earth, I'd give up software dev. and open a hot dog stand :-)
>

Comic relief??? Sadly, I think there is some unfair prejudice regarding VB that has crept in and taken root.

Now, if you had said that we need to directly communicate with a printer driver and that would involve unsafe code, then maybe writing that aspect of an app in C# would be the way to go...


>
I believe that 90% of the battle of .NET is the framework/classes/ado/etc - things that are largely langauge independant. Ultimately, we could have compnenets written in either and I wouldn't care - but I'll do my framework in C# fro the reasons above.
>

Make the choices you think are best. But be sure to have a sound reason for making the choice. Unfortuantely, other than the speed issue you bring up - assuming it is true, there is not one single bona-fide/rationale reason listed above for the decision you are making. And the speed one is flimsy at that. Your analysis is very skewed here. Have you looked at VB at all? Or, is what you know based on what Kevin has told you?