C# verses VB.Net Which Way to go

[Robert Lario]

C# verses VB.Net Which Way to go. I am sure this issues has come up before.
Please direct me to any good articles that cover this issue. Ideally some
neutral assessment.

Thanks

Robert

[Kenneth Baltrinic]

As a VB programmer for 10 year, I concur with this. I have had a lot of
luck learning c# while trying to work in vb.net is like programming with my
knuckles. I feel like nothing makes sense. But then I've been a c++ wanabee
my entire career, so the farther I get from vb the cluckier it feels.

--Ken

"Girish Bharadwaj" <girishb@nowher e> wrote in message
news:%2******** ********@TK2MSF TNGP11.phx.gbl. ..

Nicholas Paldino [.NET/C# MVP] wrote:

Robert,

If you are trying to evaluate for an organization, and you want to
leverage existing skill sets, then you will want to go with the .NET
language that is similar to what your organization already knows. For
example, if you come from a VB shop, then you will want to use VB.NET. If you come from a C++ shop, then Managed Extensions for C++ or C# would
probably be the best route to go.

However, with few exceptions, there really is little difference between the languages. All of the functionality is in the base class libraries
anyways.

Hope this helps.

The funny thing that I found out form MS evangelist is that one thing
that they have noticed is that VB 6.0 programmers get used to C# pretty
quick (more than VB.NET). He was saying that this might be because
VB.NET just enough different to cause enough headaches to someone who
has already done a lot of VB programming.
With C#, they approach it as a new language and pick it up pretty good.
All in all, I think going with C# usually seems like a best bet since
going to and from VB.NET isn't that hard after that.

--
Girish Bharadwaj

[Daniel Billingsley]

I agree Eric, and I'm betting on C# because I think as they diverge in the
future the mission statement for VB.Net will tend to be back towards the
less-technical RAD roots and C# will be the more technically advanced
option. Who knows, but that's my prediction. I think in a few years there
will be"C" and Java developers in one "class", and everyone else. All
completely and absolutely my conjecture and opinion.

"Eric Cadwell" <ec******@ns.in sight.com> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..

I'm being a little dramatic. It's more and more likely that as .NET matures that you wouldn't need to go unmanaged. I suppose the line won't be crystal clear, but if you know C# and don't have some C/C++ background, then you
won't qualify for all C# positions. In a tough market that could mean months of unemployment.

I still think that the market will drive the expectation of a C# programmer to be much more skilled than a VB.NET programmer. Most classic VB
programmers were so abstracted from the OS and don't truely know how things work.

-Eric

[Cor]

Daniel,

Today I was busy with a routine in a VB.net program with a very deep nested
if else.

I find that structure from VB.net dump, all those useless "IfElse" and
"then"

Then I did thought what it would look in a probram language that uses {} for
it.

It would be unreadable. This is an aspect from VB I did not like, and what
is a major difference between VB and all other modern languages, but with a
deep nested if and the help from the IDE, VB.net gives very nice readable
code.

I am not so sure that it will be a C, or J, or VB language

I hope that there will be in future a languages who has all goods from both
sides.

Just a thougth as answer on your message.

Cor

[Eric Cadwell]

Exactly, I took up C# knowing that I'd have to raise my game a notch or two.
Anyone coming into C# should at least consider that the competition for jobs
will be a lot tougher. Your can't just commit to learning C# and the
Framework libraries, your going to have to dig deeper.

The only issue mudying the waters is ASPX. It would seem that you can go Web
Forms and limit your knowledge to what the Framework provides.

There will always be a need for two levels of resources, but whether C# and
VB.NET will define them is yet to be seen.

-Eric