c# vs vb.net

[Pohihihi]

For fair reply cross posting on VB ng as well.
I am currently reading this article (on attributes) and article has examples
both in VB and C#. This question never hit me before but I guess because
since last few days I have started thinking about going back to VB and learn
VB.Net and mixed with this article giving examples in both the languages I
have to ask my self "Why should I learn VB.Net when I am doing good in C#".

Basically I am interested in knowing what are the technical (or deep
technical) and professional advantages I might get by learning VB.Net
(beyond what they have on MSDN). I started with VB (v4) and kind of stopped
using it all together after C# came out. VB is a fine language but I need to
have a compelling reason to go back and catch up with new VB.Net.

Your input?

Thanks,
--
Po

[Dennis]

With VB.Net, you don't have to worry about which } matches which }...that's
reason enough for me.
--
Dennis in Houston
"Pohihihi" wrote:

For fair reply cross posting on VB ng as well.
I am currently reading this article (on attributes) and article has examples
both in VB and C#. This question never hit me before but I guess because
since last few days I have started thinking about going back to VB and learn
VB.Net and mixed with this article giving examples in both the languages I
have to ask my self "Why should I learn VB.Net when I am doing good in C#".

Basically I am interested in knowing what are the technical (or deep
technical) and professional advantages I might get by learning VB.Net
(beyond what they have on MSDN). I started with VB (v4) and kind of stopped
using it all together after C# came out. VB is a fine language but I need to
have a compelling reason to go back and catch up with new VB.Net.

Your input?

Thanks,
--
Po

[MstrControl]

Hi,

Well... I believe that, for most people, choosing a language nowadays
is more like choosing a religion than actually choosing a tool.

I had attended to a seminar on Devdays a couple years ago when the
dotNet platform was being introduced... you can imagine the roar of the
attendance... the speaker had just spoken something that strucked me
like a thunderbold: "you will not be C developers or VB developers...
you will be DOT NET developers!"

And for some reason the guy was right. As far as I know, everything
done in C# can be done in VB.Net and vice-versa.

So, for me, choose the language you feel more confortable with. VB, C#,
Delphi, Cobol, Lua... it really doesn't matter as long as you deliver
the goods and it works for you. :-)

As for myself... I've chosen VB... Why? Wel... because I've been using
VB since the earlier days of the VB for DOS. And keeping upgrading
since then.. os it was simply a natural choice for me. But that's just
me. :-)

Regards,

Paulo

[dfoster]

On 2005-08-24, Pohihihi <po******@hotmail.com> wrote:

For fair reply cross posting on VB ng as well.
I am currently reading this article (on attributes) and article has examples
both in VB and C#. This question never hit me before but I guess because
since last few days I have started thinking about going back to VB and learn
VB.Net and mixed with this article giving examples in both the languages I
have to ask my self "Why should I learn VB.Net when I am doing good in C#".

Basically I am interested in knowing what are the technical (or deep
technical) and professional advantages I might get by learning VB.Net
(beyond what they have on MSDN). I started with VB (v4) and kind of stopped
using it all together after C# came out. VB is a fine language but I need to
have a compelling reason to go back and catch up with new VB.Net.

Technical reasons? there aren't any. The language constructs are so
similar that you don't even get the benefit of looking at things a
different way, as you would if you learned F# or something. Being
familiar enough to VB to be able to read VB code is useful in case you
find code samples or something, but that just takes a few minutes.

Professional reasons? That's impossible to say without knowing more
about what you do. Obviously, knowing VB is going to increase the
opportunies available to you, but whether that matters or not depends
on your situation. If you ever need VB, it just takes a few days to
become pretty proficient with it if you know C#.

[Workgroups]

Keep C#. You can't go wrong familiarizing yourself with "C-based"
syntactical stylings.

"Pohihihi" <po******@hotmail.com> wrote in message
news:OF**************@TK2MSFTNGP15.phx.gbl...

have to ask my self "Why should I learn VB.Net when I am doing good in
C#".
Your input?

[Jeff Ptak]

There is no technical reason to go to C#. I know both languages. When it
comes to .NET programming many times the only difference between VB & C# is
the ";" at the end of the line. There is no performance gain by going with
the C-based language as there was when choosing between VB6 and C++.

Personally, I prefer VB and I can't wait for Visual Studio 2005...

"Pohihihi" <po******@hotmail.com> wrote in message
news:OF**************@TK2MSFTNGP15.phx.gbl...

For fair reply cross posting on VB ng as well.
I am currently reading this article (on attributes) and article has
examples
both in VB and C#. This question never hit me before but I guess because
since last few days I have started thinking about going back to VB and
learn
VB.Net and mixed with this article giving examples in both the languages I
have to ask my self "Why should I learn VB.Net when I am doing good in
C#".

Basically I am interested in knowing what are the technical (or deep
technical) and professional advantages I might get by learning VB.Net
(beyond what they have on MSDN). I started with VB (v4) and kind of
stopped
using it all together after C# came out. VB is a fine language but I need
to
have a compelling reason to go back and catch up with new VB.Net.

Your input?

Thanks,
--
Po

[Allen St.Clair]

I choose VB.Net.
because:
1 I was VB6 developer.
2 I hate to use Shift very often (When typing "System." in c# ... hell...)
"Pohihihi" <po******@hotmail.com> wrote in message
news:OF**************@TK2MSFTNGP15.phx.gbl...

For fair reply cross posting on VB ng as well.
I am currently reading this article (on attributes) and article has
examples
both in VB and C#. This question never hit me before but I guess because
since last few days I have started thinking about going back to VB and
learn
VB.Net and mixed with this article giving examples in both the languages I
have to ask my self "Why should I learn VB.Net when I am doing good in
C#".

Basically I am interested in knowing what are the technical (or deep
technical) and professional advantages I might get by learning VB.Net
(beyond what they have on MSDN). I started with VB (v4) and kind of
stopped
using it all together after C# came out. VB is a fine language but I need
to
have a compelling reason to go back and catch up with new VB.Net.

Your input?

Thanks,
--
Po

[mmitchell]

It makes no difference when it comes to the finished application. It
does seem to me though that there are more examples in C# on the web. I
also have found that being a contractor, I have better luck finding
jobs with C#. I happen to know both vb.net and C#. It's not hard to
cross over and certainly makes you more valuable.

[Pohihihi]

Thank you everyone for the input.
"Pohihihi" <po******@hotmail.com> wrote in message
news:OF**************@TK2MSFTNGP15.phx.gbl...

For fair reply cross posting on VB ng as well.
I am currently reading this article (on attributes) and article has
examples
both in VB and C#. This question never hit me before but I guess because
since last few days I have started thinking about going back to VB and
learn
VB.Net and mixed with this article giving examples in both the languages I
have to ask my self "Why should I learn VB.Net when I am doing good in
C#".

Basically I am interested in knowing what are the technical (or deep
technical) and professional advantages I might get by learning VB.Net
(beyond what they have on MSDN). I started with VB (v4) and kind of
stopped
using it all together after C# came out. VB is a fine language but I need
to
have a compelling reason to go back and catch up with new VB.Net.

Your input?

Thanks,
--
Po