C# or VB

[Guest]

Hi, I've been developing in VB for around 5 years. I've just had a look at C#
& it looks very nice. I'm deciding on which path I should take; VB.NET or
C#.NET.
If I choose to focus on C#, will it be easy to switch to VB.NET should I
have the need to? Will I need to do any additional study or will my VB
knowledge be ok?
Thanks for your opinions
Ant

 

[BrianGlacain]

Hi, I've been developing in VB for around 5 years. I've just had a look at
C#
& it looks very nice. I'm deciding on which path I should take; VB.NET or
C#.NET.
If I choose to focus on C#, will it be easy to switch to VB.NET should I
have the need to? Will I need to do any additional study or will my VB
knowledge be ok?
Thanks for your opinions

When I moved to .Net, I had previously worked with C/C++ and Visual Basic
but I went with C# simply because I much prefer the structure and syntax of
C-based languages. Most of my work has been in C# although I have created a
few modules in VB.Net, mainly to use late-binding. The biggest hurdle
programmers new to .NET face is the .NET Framework itself, not VB or C#
syntax. If you learn C# you would pick up VB.NET really easily, and vice
versa.

 

[Sb]

This is only my idea:
As a VB 6 developer i moved to .NET and started from VB.NET . You know, it
is no VB 6 to compare with. It is more C# like and a way too different from
its illegitimate sister, VB 6. I worked with VB.NET for a year, but needed
more control on library developing ( like code commenting, operator
oveloading, and so on...) So I moved to C# and it was a very easy move,
believe me , i learned C# in less than a week! Actually it is all the
framework which is all the same for any .NET language.
Now i do this:
work on abstract programming and infrastructure with C#, while i create the
UI and Windows applications using VB.NET
It is really nice to do things like that.
It is also importatnt to take a look at VB.NET 2005. It has so many new and
sexy features that takes my breath away! (Just to mention the "My" keyword
and new operator overloading, code commenting and ...)
Finally, gotto mention that the real thing to learn is the framework and its
rich set of classes. Pick VB.NET or C#.NET or both. Not so much different
languages now... or learn them both.
It is all your taste that matters.

 

[QAS]

C#

 

[Guest]

Thanks all, I think you’ve consolidated my suspicions. C# sounds like the go.
So long as it’s easier to switch back to VB, (which you point out it is) I
think I’ll go C#. By the brief look at it, it seems quite a ‘key stroke
efficient’ way of coding & not overly complicated either. The only draw back
I could pick up is that you can’t late bind but that’s not really a problem
anyway as I don’t late bind generally. Now for the .NET framework…
Thank you