Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • True, both can do 98% that the other can BUT there is so much rope to hang yourself with in VB. On Error Resume Next alone would send me running towards C#. The Module concept also is very dangerous. It is similar to a static class in C# but... everything in it is globally accessible without reference to the parent class and automatically static w/o any other indication... except that the parent class is a Module...! Commented Jan 11, 2011 at 16:33
  • 6
    Sorry to nitpick but this just isn't true. For example, how would you write an exception filter in C#? blogs.msdn.com/b/clrteam/archive/2009/08/25/… Commented Jan 11, 2011 at 16:34
  • @LukeH To add exception filter to C#, we can build a function in VB or IL, then call it in C# :D Commented Jan 11, 2011 at 16:39
  • 4
    @Anna: Thus disproving your statement that "everything you can do in VB.NET you can do in C#". Commented Jan 11, 2011 at 16:42
  • 2
    There are quite a few things that you simply cannot do in VB.Net that you can in c# -- see also: stackoverflow.com/q/2362381/50447 Commented Jan 11, 2011 at 17:23