The company I used to work for (big, multibillion-dollar insurance company) had a lot of VB.NET projects (and C# projects, and Java projects, and anything you m

The company I used to work for (big, multibillion-dollar insurance company) had a lot of VB.NET projects (and C# projects, and Java projects, and anything you might care to think about). In particular, the manager at the branch I worked in had settled on VB.NET because he thought it would be an easier transition for the old VB6 developers he had. And it's not bad, I loved not having to worry about case sensitivity and stupid brackets and semicolons, but that's only syntactic sugar. I'm now back to C# for the last few years and I noticed no significant difference, other than more resources on the web.