C# v VB.NET - any research on usage?

[Robin Tucker]

I need to find some documents/research for my manager about VB.NET v C# use.
I've noticed that there are many more people using C# than VB.NET, that
there seem to be more job vacancies specifying C# and projects written with
it.

I would basically like any links you might have to articles with
non-anecdotal evidence for usage patterns, if there are any.

Thanks,
Robin

[jeremiah johnson]

i realize this isn't what you asked for, but i have some anecdotal
evidence for VB.

Everywhere I've worked that did MS development work, VB was used *far*
more than C#. Personally, I despise VB and do all .net work in C#, but
i'm clearly in the minority with that attitude.

in the VB world that I've seen, C# is something you graduate to after
long years doing VB work. C# pays more (usually) and is a bit more of a
respected language from what I've seen.

sorry to inject something you didn't ask for, but i felt it was
something you should read, given your thoughts on C# vs VB usage.

Robin Tucker wrote:

I need to find some documents/research for my manager about VB.NET v C# use.
I've noticed that there are many more people using C# than VB.NET, that
there seem to be more job vacancies specifying C# and projects written with
it.

I would basically like any links you might have to articles with
non-anecdotal evidence for usage patterns, if there are any.

Thanks,
Robin

[Cor Ligthert [MVP]]

Robin,

Your question is probably very regional (country/state) if you say I
see............ .., here (Holland) I see it more and more asked like this

..Net Developer (VB, C#, AdoNet etc.)

I hope this helps,

Cor

[Robin Tucker]

sorry to inject something you didn't ask for, but i felt it was
something you should read, given your thoughts on C# vs VB usage.

No thats fine. I don't mind anecdotal evidence, it's just not too useful
when discussing which language to use for which project with a line manager.
I'm using VB.NET myself at the moment but whenever I need to incorperate
code from the outside world, the chances are it will be written using C#.
So, actually, my project consists of my main application and associated
libraries, with a few other libraries in C#. I'm not sure the mixture is
too aesthetically pleasing - at least it won't be for the maintenance guy
who comes after me.

[Ian]

jeremiah johnson wrote:

i realize this isn't what you asked for, but i have some anecdotal
evidence for VB.

Everywhere I've worked that did MS development work, VB was used *far*
more than C#. Personally, I despise VB and do all .net work in C#, but
i'm clearly in the minority with that attitude.
I disagree and don't think you are alone. There are thousands of
programmers
who evolved from the 'c++' syntax of programming who favour c#. Whilst
programmers who liked c and c++ put back software engineering decades,
we're thankfully over it now. Most of the features implemented in Ada
are now
standard in modern languages, despite your c++ crowd mentality, and the
only
thing left to get rid of, is the stupid symbolic ambiguous style that
breeds
programming errors.

Fortunately, the days when in a programming language you could have
a line which could semantically and syntactically be valid by changing
a single character are coming to an end.

When (i += j) and (i -= j) and (i == j) and (i != j) and (i == -j) etc
all compiled
there was no chance of reliability, and or productivity, because people
find
it hard to see these errors.

in the VB world that I've seen, C# is something you graduate to after
long years doing VB work. C# pays more (usually) and is a bit more of a
respected language from what I've seen.
Yes it does, but this isn't because of anything inherent in the
language,
a 100 IQ programmer who is an expert in vb.net is more productive
than a 100 IQ c# programmer.

It's a side effect of history. VB was easier to learn but not as
powerful.
c++ was harder to learn but more powerful. Thus the typical c++ becomes
c# guy is more experienced on average.

This may mean that advantage is self fulfilling, but there's no
language
reason for it.

sorry to inject something you didn't ask for, but i felt it was
something you should read, given your thoughts on C# vs VB usage.

Robin Tucker wrote:

I need to find some documents/research for my manager about VB.NET v C# use.
I've noticed that there are many more people using C# than VB.NET, that
there seem to be more job vacancies specifying C# and projects written with
it.

I would basically like any links you might have to articles with
non-anecdotal evidence for usage patterns, if there are any.

Thanks,
Robin

[m.posseth]

Hello robin

http://www.advisor.com/Articles.nsf/aid/SHERP42

I've noticed that there are many more people using C# than VB.NET, that
there seem to be more job vacancies specifying C# and projects written
with it.
There seems to be a shift in MCSD certification to C# that is a fact ,
however in usage i believe that it is still 60/40 ( in favor of VB )
probably for the fact that VB is a more forgiving language as others

I would say learn both languages they have both there strong and weakpoints
, i prefer VB only because i have a Basic background however i can also
read and write C# code , but i noticed that i am far more productive in
VB.Net

there is no serious advantage to either language. It is purely down to
which syntax you are happiest with using
regards

Michel Posseth [MCP]



"Robin Tucker" <no****@nomeans no.com> schreef in bericht
news:dk******** ***********@new s.demon.co.uk.. .I need to find some documents/research for my manager about VB.NET v C#
use. I've noticed that there are many more people using C# than VB.NET,
that there seem to be more job vacancies specifying C# and projects written
with it.

I would basically like any links you might have to articles with
non-anecdotal evidence for usage patterns, if there are any.

Thanks,
Robin

[m.posseth]

well i do not see anything bad in this at all , a current project i am
working on has some parts written in C# and some parts written in VB.Net

just for the fact that example code and documentation for some parts of
programming are more common to be delivered in C# as VB.Net ( cryptography ,
Compression etc etc ) in other parts VB is more to be found out there
Remoting , COM interop for instance

so why don`t mix those in a project ( both tasks can also be done in both
languages ) as you would become more productive

regards

I prefer to call myself a VS6 and a VS.net programmer

who just favors VB

Michel Posseth [MCP]

"Robin Tucker" <no****@nomeans no.com> schreef in bericht
news:dk******** ***********@new s.demon.co.uk.. .

sorry to inject something you didn't ask for, but i felt it was
something you should read, given your thoughts on C# vs VB usage.

No thats fine. I don't mind anecdotal evidence, it's just not too useful
when discussing which language to use for which project with a line
manager. I'm using VB.NET myself at the moment but whenever I need to
incorperate code from the outside world, the chances are it will be
written using C#. So, actually, my project consists of my main application
and associated libraries, with a few other libraries in C#. I'm not sure
the mixture is too aesthetically pleasing - at least it won't be for the
maintenance guy who comes after me.

[Andrew Morton]

Robin Tucker wrote:

... that there seem to be more job vacancies specifying C#

That could also happen if there was a high turnover of C# programmers.

Andrew

[Denis Dougall]

I disagree with some of the points Ian made but from an industry standpoint
I think there are more VB coders because it is an easy language to learn and
tends to develop design methodologies required for using / abusing APIs .
As you travel through C, C++ and end up at whichever .NET language the
knowledge of assemblies and DLLs can only help in your advancement. On a
personal note, my preferred scripting language is jscript, most web facing
containers/apps are Java but I don't know a stitch about J#.. Odd!

The turn over (if defacto) in C# programmers I find interesting but there
will always be a larger pot of VB coders than C# programmers.

Denis

"Andrew Morton" <ak*@in-press.co.uk.inv alid> wrote in message
news:O%******** ********@TK2MSF TNGP09.phx.gbl. ..

Robin Tucker wrote:

... that there seem to be more job vacancies specifying C#

That could also happen if there was a high turnover of C# programmers.

Andrew

[Jim Underwood]

There is a problem with using both languages in a project, or even in a
company.

Certain programmers know certain languages and if everyone writes code in
their personal favorite langauge you end up with 4 programmers each writing
code that only they understand. Maintenance becomes a nightmare as no one
can work on more than one piece of the application.

If everyone in your environment knows C#, Java, VB, etc. then it doesnt
matter which languages you mix and match, but this is seldom the case. It
is important to have standards regarding which langauge should be used in
your environment in order to maintain consistency and maintainability .

Personally, I have no problem switching from VB to C# as it adds to my skill
set, but I would never write code that the rest of the organization does not
know unless there was no choice.
"m.posseth" <po*****@planet .nl> wrote in message
news:et******** *****@TK2MSFTNG P09.phx.gbl...

well i do not see anything bad in this at all , a current project i am
working on has some parts written in C# and some parts written in VB.Net

just for the fact that example code and documentation for some parts of
programming are more common to be delivered in C# as VB.Net ( cryptography , Compression etc etc ) in other parts VB is more to be found out there
Remoting , COM interop for instance

so why don`t mix those in a project ( both tasks can also be done in both
languages ) as you would become more productive

regards

I prefer to call myself a VS6 and a VS.net programmer

who just favors VB

Michel Posseth [MCP]

"Robin Tucker" <no****@nomeans no.com> schreef in bericht
news:dk******** ***********@new s.demon.co.uk.. .

sorry to inject something you didn't ask for, but i felt it was
something you should read, given your thoughts on C# vs VB usage.

No thats fine. I don't mind anecdotal evidence, it's just not too useful when discussing which language to use for which project with a line
manager. I'm using VB.NET myself at the moment but whenever I need to
incorperate code from the outside world, the chances are it will be
written using C#. So, actually, my project consists of my main application and associated libraries, with a few other libraries in C#. I'm not sure the mixture is too aesthetically pleasing - at least it won't be for the
maintenance guy who comes after me.