>>This is very interesting Craig. I started learning C# a couple of years ago actually and wrote a couple of little modules in it. Nothing hardcore. I was still leaning towards C# because of the huge amount of code samples available out there on the web. Now, it's looking like vb.net may be a better choice for developing full-fledged apps in the long haul and using c# behind the scenes. Time to pull out the vb.net book I guess :o)
>
>Hi Tracy. In the early days of .NET many VFP guru insisted that C# was the way to go. Then almost overnight many of them started to say VB.NET was the way. I attribute this to Calvin and a few other high profile Fox people joining the VB.NET team. Who knows, maybe the tide will flow the other way again.


I think it has to do with the mindset of the people who switched. Many of us who started to learn C# when it was still Cool ('Cool' was the codename of C#), did so because they just loved to play with the technology.

I think people who get their first exposure to .NET because of business reasons tend to go more with VB. Really, you gotta be kind of a geek to like the C# syntax.

But as I said before: Choice of language is really not a big deal. Go with whatever appeals more to you. Technically, there is very little difference. VB.NET currently has a big push towards more productivity. But guess what: When you talk to the C# team, you get the same message.

It is just like Rod always says: Comparing VB and C# is like comparing English to Spanish. Go with the one you know (or feel you can pick up more easily). Beyond that, they both get the job done equally well...

Markus