Timeline for VB.Net vs C# debate
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 18, 2012 at 15:32 | comment | added | supercat | With each generation of tools, the "features" arguments shift a bit. The only thing I can think of which C# has as of vs2010 which vb.net lacks is iterators; by contrast, vb.net offers named indexers, exception filters, XML literals, a an "Is" operator that's 1000x better looking than Object.ReferenceEquals, event handling that's almost done right, and a smoother IDE experience. VB.net makes it possible, albeit slightly awkward, to have field initializers use constructor parameters or safely create IDisposable objects without having to use ThreadStatic variables; C# does not. | |
| Oct 7, 2010 at 23:02 | comment | added | Kyralessa | This is where I'm at. I'm still fond of VB, as it's where I got my start, but in my opinion C# has better syntax in things like lambda expressions. On the other hand, VB has XML Literals, which C# can only dream of. I think it's worth breaking off a separate VB project for heavy XML work. | |
| Sep 16, 2010 at 20:48 | comment | added | Note to self - think of a name | "features coming to C# first" It's not always that way, though. See stackoverflow.com/questions/181188/… (Just to throw another spanner in the works) | |
| Sep 7, 2010 at 7:10 | history | answered | Josip Medved | CC BY-SA 2.5 |