3 ms·
Because a lot of businesses have codebases in VB. My company moved to C# for new development long ago, but we still have maybe 20% of our codebase in VB. It's n
by archon 11y ago
Because a lot of businesses have codebases in VB. My company moved to C# for new development long ago, but we still have maybe 20% of our codebase in VB. It's not worth the time it would take to convert it, so it stays in VB. It's nice that Microsoft continues to support VB for companies like mine where being required to move to C# would cause a lot of problems for us.
- bigdubs 11y agoTake binary. Open in IL Spy, switch language to C#. Done.
- maximilianburke 11y agoAnd lose all code comments, revision control history, etc. Not to mention the risk of doing that on a large scale.
- bigdubs 11y agoI've done this before on a large scale (vb=>c#). You don't lose revision control history, thats still in the history for the previous file. If you're doing things in vb that can't be done in c# (there are a few things), you're writing bad code. The risk is greater in using bad technology / having legacy code.
- samsaga2 11y agoYou can use telerik converter. It's free and it works pretty well. http://converter.telerik.com http://converter.telerik.com
- thebouv 11y agoI can see why VB is used in large codebases for legacy apps. What I don't understand is continuing to work on the language and releasing v14 with improvements. That's just encouraging legacy code to stay the way it is, albeit with some new sugar.