title: Any value gained in converting a legacy code base from VB to C#?
body: <p>Quick searches on the topic result in articles such as:</p>
  
  <ul>
  <li><a href="http://www.simple-talk.com/dotnet/.net-framework/10-reasons-why-visual-basic-is-better-than-c/" rel="nofollow noreferrer">10 Reasons Why Visual Basic is Better Than C#</a></li>
  <li><a href="http://www.vbrad.com/article.aspx?id=65" rel="nofollow noreferrer">Top 10 reasons VB.NET is better than C#</a> (old article)</li>
  </ul>
  
  <p><a href="https://softwareengineering.stackexchange.com/questions/1180/vb-net-vs-c-debate">This thread</a> over at the programmers stack exchange even presents some interesting and humorous arguments but most center around culture, syntax, and learn-ability. <a href="http://geekswithblogs.net/GruffCode/archive/2012/12/13/converting-vb-.net-to-c-a-post-mortem.aspx" rel="nofollow noreferrer">This article made the "technical debt" argument for why they performed the conversion.</a> Basically, everyone wanted to stop using VB.NET.</p>
  
  <p>I don't expect to drastically change the code base of a legacy system for any of the above reasons. However, the current system has major issues: poor performance and substantial logic errors. But this alone does not merit a conversion, does it? It should also be noted that the developers are equally strong in each language so that doesn't have a bearing on the question.</p>
  
  <p><strong>Are there any substantial benefits, such as performance gains, that would be achieved by converting 65K lines of code from VB to C#?</strong> </p>
  
  <p>After my research, I'm not convinced that a conversion would be beneficial. </p>