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
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;
C# seems to be shading it in the job ads. Pity though, as VB.Net is more readable (and therefore more maintainable) IMO...
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.
"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-)
I do my DLL's - Classes in C# For the XML Comment features. :-)
Is there an easy way to use c# in a vb.net project?
It's not possible. It has to be in a separate project.
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.