Justification of using C# over VB.NET

  • Thread starter Thread starter Jack
  • Start date Start date
J

Jack

Hi,

I'm starting on a new project to develop Windows application run on
the .NET Frame work. Would you please give me some justifications to
present to management on why we should use C# over Visual Basic .NET.

Right now we don't have any code written for the .NET yet and this
would be a new project.

I preferred C# because my background in programming is in C#/C++/C/Pro
C and Java.

Thank you in advance.

Jack
 
Hello Jack

Small things like:

C# has XML Comment option, which VB.NET just can't do.
The C# compiler has more errors and warnings e.g. it detects if part of you
code is not reachable.
C# is a native .NET language. In VB.NET you have several way of doing the
same things, because it history, e.g. Loop... While/End While. And
CInt(myString)/Convert.ToInt32(myString).

VB.NET has background compile, which is great but requires a fast machine.
VB.NET has automatic code indent (in C# you have to delete and type the
ending } again).
I my opinion VB.NET programmers are likely to be cheaper, but more focused
on RAD. C# Developers are likely to be more dedicated to programming.

In the Next Version of VS.NET C# is a superior language, because it has
refractoring and VB.NET has not. VB.NET was supposed to be the only language
which would get Edit-And-Continue... but I look likes C# is getting this as
well.

With you background I would chose C# anytime. With a VB.NET background I
would also chose C# if I was going to write big solutions, and spend 14 days
on learning the difference between C# and VB.NET (it took me 3 days!).

BTW: I'm a VB.NET developer.

PS: I would love if Microsoft synchronized the two languages, so these small
things was a argument for choosing one language over another.

Thomas
 
I'm starting on a new project to develop Windows application run on
the .NET Frame work. Would you please give me some justifications to
present to management on why we should use C# over Visual Basic .NET.

Right now we don't have any code written for the .NET yet and this
would be a new project.

I preferred C# because my background in programming is in C#/C++/C/Pro
C and Java.
Click to expand...

That's a pretty good reason, to be honest.

See http://www.pobox.com/~skeet/csharp/faq/#vb.or.csharp for some more
reasons in each direction.
 
Good reason, there are not more.
Click to expand...

There are, although they don't affect everyone.

If you really want to overload operators or write managed but unsafe
code, and you don't want to wait for Whidbey, you can't use VB.NET.
 
Hi Jon,

I had sended this before I saw you had sended it also.
:-)

I read top down today.

Cor
 
There's very little reason to choose one over the other. VB.NET has a much
friendlier IDE. C# allows unsafe code blocks and operator overloading and
XML Comments. If you use Option Strict in VB.NET, performance is virtually
identical.

You can mix projects in a solution. All breaks donw to the same code by and
large. If you are going ot use .NET, learn the FRAMEWORK. Learn ADO.NET.
Syntax is trivial. I see too much terrible code in both languages to
advocate one over hte other (I use C# b/c I knew C++ and Java and that's
it). A top notch C# developer can learn VB.NET in a week or two and vice
versa. A top notch VB6 or VC++ programmer can't learn either language in a
week or two, it'd take a good half a year to really know your stuff.

So basically tell them that the summation of the distinction between the two
languages doesn't amount to a hill of beans in most instances. If you use
one and don't like it, you can swtich to the other, and still use your old
code. VB.NET and C# live very happily together in the same solution.
 
There are add ins that can be downloaded that will allow VB.NET to do all
the XML comment stuff, but yes, it's more of a pain and doesn't come
installed.
 
Hello Marina

I've seen these. But the ones I've seen doesn't include the comments when
compiling, so that you can see the comments in intelliscense. You can only
get an XML file, which you can compile into a help file.

Thomas
 
Back
Top