Tuesday, March 13, 2012

Should I now learn C# or continue with VB.NET?

Hi there,

I've been using VB.NET for 2+ years (on and off) and was told by an Job Agent today that there are more and more jobs wanting C# then VB.NET.

I'm going to take MCSD, should I learn C# whilst studying then takes C# exams? Or stick with VB.NET.

I know agents wont put you forward to C# jobs if you dont have commercial experience even though we use the same features in VB.NET.

Any feedback from the users here is greatly appreciated.

I personally believe that you should be bi-lingual and know both C# and VB.NET. They are somewhat similar, so learning C# after you've learned VB.NET shouldn't be that big of a challenge.
Hello, I would consider that you learn C# atleast the structure and the format. Just in case you ever have to do some Java coding, you would have no problem in tackleing that task. Since C# and Java are pretty close when it comes down to structure and formatting.
But should I stop right now VB.NET, and start practicing writing C# using my self-paced MCSD book. I know it's my decision, but what's the learning curve?

You have to decide what is best for yourself.

I can tell you that the learning curve for C# is primarily centered on syntax. C# does not support implicit type casting/conversion like VB.Net does, which I've found many VB.Net programmers struggle to get the hang of. If you're using VisualStudio, the way the IDE completes code, gives code hints, etc. for C# as compared to VB.Net is different. So, the rhythm of writing code is also different. These are the things that I noticed the most when learning C#. But don't read too much into this...the learning curve is not steep at all.

-- Dan Fields

0 comments:

Post a Comment