C# and VB.NET

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Why does C# seem to get more "play" in the .NET world? Don't both of these
languages compile to the same IL language. I know both languages has its own
little features; but when I look at job postings I get concerned when I see
verbage like "C# is a Must". I program mostly in VB.NET; but I don't think
it will take me that long to get use to the c# style. Programming in .NET
language shouldn't matter right? Anyone else would like to comment?
 
Tampa said:
Why does C# seem to get more "play" in the .NET world? Don't both of
these languages compile to the same IL language. I know both
languages has its own little features;
Click to expand...

Hi,

The difference will slowly vanish with time. The next flavor of VB .Net
will have the same features a C#, like generics or operator overloading.
The choice will only be a matter of personal preference.
 
VB is seen by many employers as a 'Toy' Language. No longer true, but do you
want to pit your career against the combined "wisdom" of all those IT
directors?

(This isn't helped by Microsoft proclaiming that the .NET framework was
written ENTIRELY IN C#)

IM(ns)HO

David
 
Tampa said:
Why does C# seem to get more "play" in the .NET world? Don't both of
these
languages compile to the same IL language. I know both languages has its
own little features; but when I look at job postings I get concerned when
I see
verbage like "C# is a Must". I program mostly in VB.NET; but I don't
think it will take me that long to get use to the c# style. Programming in
.NET language shouldn't matter right? Anyone else would like to comment?
Click to expand...
I have detected a couple of features that are not in VB.NET
1. Targetting Attributes: field
2. using keyword
There are more
 
Back
Top