Picking between C# and VB.NET is largely a personal decision. Both languages are mature, straightforward, and you can effectively do the same things identically in both languages. If you were to convert C# to VB.NET or vice versa, you can effectively do a line-by-line translation. Some developers work only in one language, but most can switch back and forth. Right now, I am working on multiple C# and VB.NET applications simultaneously. Other than occasionally starting to write in the wrong syntax, it’s no problem. Personally, I do prefer C#, but it’s neither a big deal nor a deal-breaker to work in VB.NET.
Here are some important points to help guide your decision.
For game development, 3D modeling, sophisticated rendering, or other very processor intensive stuff, you’re better off choosing C#/XAML. It’s the only option for DirectX integration, and you won’t have to worry about performance issues and limits.Advantage: None. It depends on the kind of apps you do.
8925 N Meridian St., Suite 115
Indianapolis, IN 46260
eImagine Technology Group is a full-service IT solutions provider using technology as the tool to help solve our clients' business problems for over 15 years.