Why I write in Both C# and VB.NET

My blog has moved.
You can view this post at the following address:
http://www.osherove.com/blog/2003/7/1/why-i-write-in-both-c-and-vbnet.html
Published Tuesday, July 01, 2003 9:09 PM by RoyOsherove
Filed under:

Comments

Tuesday, July 01, 2003 10:27 AM by Lawrence Oluyede

# re: Why I write in Both C# and VB.NET

Very nice post. I use only C# but when I'll have enough time I'll check VB.NET seriously. The only thing to notice is that in my job place everybody use C# and VB.NET is forbidden :P and so I'll have to learn it in my spare time. Surely I'll do. Bye
Tuesday, July 01, 2003 11:21 AM by Chad Osgood

# re: Why I write in Both C# and VB.NET

Intellisense with enums in C# would be nice, but the consistency of the framework largely obviates any need for it. If I encounter a propery that's an enum, I can usually just pluralize the name of the property to find my enum. Worse case, I'll just hover over the property to find out what type it is.

e.g.:
Foo.FooState = FooStates.Unknown;
Tuesday, July 01, 2003 12:00 PM by Duncan

# re: Why I write in Both C# and VB.NET

C# seems to be shading it in the job ads. Pity though, as VB.Net is more readable (and therefore more maintainable) IMO...
Tuesday, July 01, 2003 5:09 PM by TrackBack

# Darrell Norton's Blog

Darrell Norton's Blog
Tuesday, July 01, 2003 5:09 PM by TrackBack

# Darrell Norton's Blog

Darrell Norton's Blog
Tuesday, July 01, 2003 6:14 PM by Chris Szurgot

# re: Why I write in Both C# and VB.NET

Even though I prefer C# to VB.NET, I have to use it for some of the programs at my job (1/2 in VB.NET and 1/2 in C#) so I use both languages frequently, and yes, I think the Intellisense on the Enums is quite a time saver, and quite a bit quicker that typing it out, or ghosting over to find out what type it is.
Wednesday, July 02, 2003 2:38 PM by SBC

# re: Why I write in Both C# and VB.NET

"The ability to keep two contrasting thoughts in the mind at the same time and think about it is a sign of fine intelligence" - Donald Rumsfeld... 8-)
Tuesday, August 12, 2003 11:46 AM by Jason Best

# re: Why I write in Both C# and VB.NET

I do my DLL's - Classes in C# For the XML Comment features. :-)
Wednesday, January 07, 2004 10:17 AM by George

# re: Why I write in Both C# and VB.NET

Is there an easy way to use c# in a vb.net project?
Saturday, January 10, 2004 3:16 PM by Roy Osherove

# re: Why I write in Both C# and VB.NET

It's not possible. It has to be in a separate project.
Wednesday, April 14, 2004 12:31 PM by konamiman

# re: Why I write in Both C# and VB.NET

I know both languages also. I prefer C# because I do not like having to write tons of useless words like Property, Function, Sub, Overloads, Next, Dim, all the EndXXX, etc. Besides I can break my code statements in several lines without having to use "_" nor any other special character, I love it! But it is also true that I miss some more intellisense in the C# editor.
Tuesday, July 06, 2004 1:46 AM by SamiMajed

# re: Why I write in Both C# and VB.NET

I've used C# for the past 2 years and ended up taking over a VB.Net project. It was interesting, because when I first learned C#, I remember having to translate every example I came accross in books and online, from VB.Net to C#, just to figure out how they worked. Now I do know both, and i still prefer C# over VB.Net.
VB.Net is definitely too verbose, I totally agree.
Also, C# tends to somehow 'force' one to be as precise as possible. It's just so much of a 'cleaner' language and therefore more enjoyable.

Cheers. :P

SamiMajed