VB.NET vs. C#

Wednesday, June 18, 2003

No -- I'm not starting another language war. I was converting some C# code to VB.NET today. After getting everything converted, I had to change the name of the class (nothing to do with the conversion). I changed it and then thought "shoot -- now I need to change all of the constuctors" (it has three overloaded constructors). Then I remembered I'm in VB.NET and all of the constructors are named "New" -- no changes required.

Yeah, I know. C# would have only been a simple search and replace. Still, in VB.NET it's nothing!

2 Comments

Why were you doing a conversion?

Jeff Julian - Wednesday, June 18, 2003 7:23:00 PM

Our company has standardized on VB.NET for development. Someone with some Java background had done some prototyping in C#. We were converting it to bring it inline with our "company standards".

Patrick Steele - Wednesday, June 18, 2003 7:28:00 PM

Comments have been disabled for this content.