Visual Basic.Net is a very capable language and can do virtually anything C# can do, so why convert? Though there are clear technical reasons, such as much better quality enforcement, the overriding reason is the growing momentum and popularity of C#, as well as the fierce animosity against VB.Net. Visual Basic started as an anything-goes hobbyist language, destroyed by Microsoft when it killed VB6, then replaced by VB.Net. It’s in a weird position of being way too complicated for its hobbyist roots, but having a lower quality and strange syntax when compared to its much bigger brother C#. It begs the question, “Why not just use C#?”
In countless surveys, C# is outpacing VB.Net in popularity, available training and tools, jobs, and salary. You don’t want to standardize on VB.Net for your company and certainly not for your career. Will Microsoft eventually kill off VB.Net like it suddenly did VB6, destroying careers and abandoning an untold number of applications? They say they won’t.