The language is a secondary issue with .NET. i.e., the functionality arises from the framework, not the language. The langauge is not an end. Rather, it is the means to manipulating the framework. Manipulating and working with the framework, that is the end...

That said, there are noticeable differences between C# and VB. Of the two, I am starting to prefer VB over C#. For most things, the choice between VB or C# is moot. I suspect that many people like to say that C# is the preferrable choice because it has the appearance of being a more "professional" langauge. Perhaps the feeling is that it is more chic. I have no doubt that at some level, using C# is *the* proper choice. But when push comes to shove, especially when you are creating database applications, your choice of language between VB and C# will not matter from a technical standpoint. From a productivity standpoint, good arguments can be put forth that make VB a better choice. For low-level framework operations, C# is proabably a better choice. For the rest of the universe that lies in the middle of the bell curve, flip a coin...