c# vs VB - which one?

  • Thread starter Thread starter David
  • Start date Start date
D

David

Hi

I am about to start a long journey.

I have good experience in Visual Basic for Applications,
and limited on VB6.

I now need to start learning either Vb.NET or c# as a
programming language. What are the benefits and
disadvanatges of each?

I would appreciate suggestions and info as to which route
to go, and any articles or links would also be
appreciated.
 
I don't know what is best for you... but I started as a VB6 programmer 4
years ago. When the beta 2 of .NET was released I started to look at .NET,
and since i knew VB6 I started with VB.NET. I thought it would make it
easier to learn .NET. It didn't take long for me to realize that VB.NET
wasn't much like VB6. Sure it has the same keywords, but the environment
itself was different. What does syntax matter anyway. I never had a
problem with the syntax of plain old 'C', I just didn't want to spend time
learning MFC or ATL or worry about separate header files. So I never go
into 'C' or C++ seriously. However when I saw the specification for C# I
got excited. Ever since I've worked exclusively with C# (since release
canidate 1).

There are "advantages" and "disadvantages" to each language. However, I
find that you can accomplish anything in either language. Each will just do
it in a different way.

The most important thing to do first is learn the framework. You can learn
a language syntax in a day.
 
C# is ok, and seems to be in demand for whatever reason. I feel that 90%
of the time its overkill, so I like to do VB.net whenever possible.

Vb.net seems more IDE-friendly to me.

Either way, you should learn how to translate from one to the other -- its
VERY easy. This way you can now put TWO skills on your resume.

One main suggestion -- GET YOURSEL THE MSDN LIBRARY. You will find out that
almost every single msdn library example is now coded both ways. And unlike
recent past, the guys at Microsofty actually did a good job documenting most
things. (not the online libraries -- they still suck). Once you get the
library installed, hook it to your dev. environment for its dynamic help.

Ciao, and good luck in your new career path.
 
Back
Top