What language is preferred to code in WinForms c# or vb.net?

[Jack Wright]

Dear All,
We would like to take a decision on what language to use to code
our WinForm applications. What is the preferred language c# or vb.net?

Please help

TALIA

Many Regards
Jack

 

[Lloyd Dupont]

C# of course !

 

[Lloyd Dupont]

a few constructive comment.

you cannot create attribute in VB
you have difficulty using byte, sbyte, short, ushort, long, ulong in VB

I don't know all the other VB limitation, but I already know that there is
no reason to bother with a limited language when you could use a new one
which was shaped to use simply and elegantly all the new features

 

[Rob Windsor [MVP]]

Hi Jack,

There's no real advantage in using one over the other so I'd suggest picking
based on which syntax you're most comfortable with. If your coming from VB 6
use VB.NET if your coming from C++ or Java go with C#.

If you are equally comfortable with both syntax and you're using Visual
Studio then I would suggest VB.NET because it has full background
compliation giving you better Intellisense and immediate notification of
compile time errors.

 

[Rob Windsor [MVP]]

Hi Lloyd,

I don't want to fuel the flames of the C# vs VB conflict but the information
in your post is pretty much just wrong.

VB.NET is not a "limited" language as you suggest, it is just as powerful
and easy to use as C# and for 99.9% of the things you'll want to do in a
WinForms app works exactly the same way as C# does.

You can create attributes in VB.NET you just can't scope them at the field
level. VB.NET has native support for Byte, Short and Long but not for
unsigned numerics (which you can still use but you have to do a lot of
casting).

On the other hand VB.NET has much better support for late-binding and
supports optional parameters, which is nice when you're using COM interop
and you don't have to pass several nulls every time you call a method.

In most respects the languages are the same, it just comes down to whether
you prefer curly braces and semi-colons or not.

 

[Mortos]

Just to add my two cents...
I could'nt agree more. Use what you're comfortable with.
Besides it won't really matter soon anyway as Miffy (www.miffy.com) will
rule the planet soon and all will wear white bunny costumes and ....

Ooops forgot myself there.

 

[Herfried K. Wagner [MVP]]

a few constructive comment.

you cannot create attribute in VB
you have difficulty using byte, sbyte, short, ushort, long, ulong in VB

I don't know all the other VB limitation, but I already know that there is
no reason to bother with a limited language when you could use a new one

Seems that you didn't play around with VB.NET enough to find out, that
the limitations you describe above do not exist.

 

[Jack Wright]

Dear All,
Thanks to everyone for their suggestions...
My suggestion would be:
1. Code our base form classes in c#. This will be done by class
programmers.
2. Application programmers should use vb.net to code their forms
for RAD.

It will be easy to train or get professional who know VB...thus get a
jump start...

One of MS .Net's Main Objective:
Code in any lanuage, you can compile and include them in a single
project.
Why have they worked towards this goal?
Reason: Different lanuages offer different levels of usability. VC++,
C# application offer unsafe code to be added...thus application
programmers can make full use of this Objective to achieve what their
applications want with the lanuage best suited.

VB.Net give application programmers RAD (Rapid Application
Development) edge.

Anyways if we decide to develop in a single language we should code in
C#.

Thanks & Regards
Jack