Hi,

I am a beginner in .NET. I have been coding in plain asp before, using
VBScript, and now when i'm migrating to .NET, i obviously chosed VB.NET.

But.... when i see code samples on net, they are mostly in C#, i also saw a
post in this newsgroup where someone mentioned that it was a very "heated
topic back in 2002 about VB.NET vs C#".

So, my question is... what was the result of that topic?
What is best to go for, VB.NET or C#? and why?

Thanks and regards

Which language you choose depends on a number of factors. If you are a
professional and have career in mind, C# is going to give you better odds at
advancing your career. In addition, as you've noticed, it is much easier to
find examples and samples written in C#. On the other hand, if you are a
casual or part-time developer, and you have little or no experience with the
C or Java language families, and are familiar with VB or VBScript, and you
are not familiar with object-oriented programming, it might be easier for
you to ease into ASP.Net with VB.Net, and worry about learning or not
learning C# later on. The difference between the programming paradigm of ASP
classic and ASP.Net is quite a learning curve. However, it might be argued
that learning C# when you start learning ASP.Net will help you keep from
falling into the trap of thinking in ASP classic terms when doing ASP.Net.

Ultimately, it's entirely up to you, and, as Led Zeppelin once said, "there
are 2 paths you can go by, but in the long run, there's still time to change
the road you're on."

--
HTH,

Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP

"M. Ali Qureshi" <(E-Mail Removed)> wrote in message
news:726AB418-B792-4C73-A8A0-(E-Mail Removed)...
> Hi,
>
> I am a beginner in .NET. I have been coding in plain asp before, using
> VBScript, and now when i'm migrating to .NET, i obviously chosed VB.NET.
>
> But.... when i see code samples on net, they are mostly in C#, i also saw
> a post in this newsgroup where someone mentioned that it was a very
> "heated topic back in 2002 about VB.NET vs C#".
>
> So, my question is... what was the result of that topic?
> What is best to go for, VB.NET or C#? and why?
>
> Thanks and regards

"M. Ali Qureshi" <(E-Mail Removed)> wrote in message
news:726AB418-B792-4C73-A8A0-(E-Mail Removed)...

> I am a beginner in .NET. I have been coding in plain ASP before, using
> VBScript, and now when I'm migrating to .NET, I obviously chose VB.NET.

Obviously??? You've clearly fallen into the trap that VB.NET is somehow an
upgrade of Visual Basic and that ASP.NET is somehow an upgrade of ASP
Classic. Apart from some peripheral syntactic similarities, nothing could be
further from the truth. The reason, of course, is the .NET Framework...

Since you're familiar with ASP Classic, you no doubt enjoy the comfort
factor of Dim This As That, If...Then...Else...End If etc... But, since
you're familiar with ASP Classic, you've almost certainly had some exposure
to JavaScript, so basic C# syntax will already be totally understandable to
you...

> But.... when i see code samples on net, they are mostly in C#, i also saw
> a post in this newsgroup where someone mentioned that it was a very
> "heated topic back in 2002 about VB.NET vs C#".

That was me...

> So, my question is... what was the result of that topic?

There was no result, because there is no right or wrong answer... Both
languages are (almost) identical in terms of functionality - the only main
advantage that C# had over VB.NET was support for unsafe code i.e. pointers.
The reason that both languages are (almost) identical is because they both
target the .NET Framework. At it most simplistic level, it really doesn't
matter at all what .NET language you use - they are all identical...

> What is best to go for, VB.NET or C#? and why?

Both, and then decide which you prefer.

It's my personal opinion that VB.NET is a totally unnecessary language, and
it exists purely for reasons of marketing. Back in early 2002, outside of
Microsoft and a tiny beta test community, there were no C# programmers at
all. But there were millions and millions of VB programmers, and Microsoft
weren't about to alienate them by releasing a new development suite with no
flavour of Basic...

Prior to .NET, I'd made my living almost exclusively with the various
dialects of Basic right back as far as QuickBasic and on through VB for DOS,
VB for Windows, VBScript, AccessBasic, WordBasic, VBA etc.

But, after about a day with C#, I knew that I never wanted to write another
line of Basic again! And, apart from one piece of work in 2004 that I simply
couldn't turn down, I never have...

However, that's just my opinion...


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

I disagree with you. Although I like C#, it's only because of a sense of
cachet that it gives you that you probably feel the way you do (because of
the fuzzy feeling you get when you think it's somehow related to C++ in some
way-- when really it's not). Aside from C#'s pointer and rudimentary
unmanaged code ability (useless in most business solutions), VB does MORE
than C#. VB event wiring is better (withevents), intellisense + syntax
checking much much better (background compiling as you type), built in
functions that wrap a lot of code up (for example, Asc, Left, Mid etc...
that handle exceptions gracefully) in both the VisualBasic Library namespace
and the handy "My" namespace. Add to that VB2008's superior LINQ/XML
implementation and you have a clear superior.

Now, you're perfectly welcome to prefer the C# syntax. But in terms of
functionality VB is not "identical" to C#... it's better.

C. Moya
http://www.cmoya.com

"Mark Rae [MVP]" <(E-Mail Removed)> wrote in message
news:%23uLjs$(E-Mail Removed)...
> "M. Ali Qureshi" <(E-Mail Removed)> wrote in message
> news:726AB418-B792-4C73-A8A0-(E-Mail Removed)...
>
>> I am a beginner in .NET. I have been coding in plain ASP before, using
>> VBScript, and now when I'm migrating to .NET, I obviously chose VB.NET.
>
> Obviously??? You've clearly fallen into the trap that VB.NET is somehow an
> upgrade of Visual Basic and that ASP.NET is somehow an upgrade of ASP
> Classic. Apart from some peripheral syntactic similarities, nothing could
> be further from the truth. The reason, of course, is the .NET Framework...
>
> Since you're familiar with ASP Classic, you no doubt enjoy the comfort
> factor of Dim This As That, If...Then...Else...End If etc... But, since
> you're familiar with ASP Classic, you've almost certainly had some
> exposure to JavaScript, so basic C# syntax will already be totally
> understandable to you...
>
>> But.... when i see code samples on net, they are mostly in C#, i also saw
>> a post in this newsgroup where someone mentioned that it was a very
>> "heated topic back in 2002 about VB.NET vs C#".
>
> That was me...
>
>> So, my question is... what was the result of that topic?
>
> There was no result, because there is no right or wrong answer... Both
> languages are (almost) identical in terms of functionality - the only main
> advantage that C# had over VB.NET was support for unsafe code i.e.
> pointers. The reason that both languages are (almost) identical is because
> they both target the .NET Framework. At it most simplistic level, it
> really doesn't matter at all what .NET language you use - they are all
> identical...
>
>> What is best to go for, VB.NET or C#? and why?
>
> Both, and then decide which you prefer.
>
> It's my personal opinion that VB.NET is a totally unnecessary language,
> and it exists purely for reasons of marketing. Back in early 2002, outside
> of Microsoft and a tiny beta test community, there were no C# programmers
> at all. But there were millions and millions of VB programmers, and
> Microsoft weren't about to alienate them by releasing a new development
> suite with no flavour of Basic...
>
> Prior to .NET, I'd made my living almost exclusively with the various
> dialects of Basic right back as far as QuickBasic and on through VB for
> DOS, VB for Windows, VBScript, AccessBasic, WordBasic, VBA etc.
>
> But, after about a day with C#, I knew that I never wanted to write
> another line of Basic again! And, apart from one piece of work in 2004
> that I simply couldn't turn down, I never have...
>
> However, that's just my opinion...
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net

"CMoya" <(E-Mail Removed)> wrote in message
news:5BBFD0DB-D307-4890-80C2-(E-Mail Removed)...

>I disagree with you. Although I like C#, it's only because of a sense of
>cachet that it gives you that you probably feel the way you do (because of
>the fuzzy feeling you get when you think it's somehow related to C++ in
>some way-- when really it's not).

Not true at all - I've never used C/C++ at all in my entire career...

> Aside from C#'s pointer and rudimentary unmanaged code ability

You mean unsafe code, not unmanaged code...

> VB event wiring is better (withevents),

WithEvents is totally unnecessary in C#, otherwise it would have it:
http://www.thescripts.com/forum/thread255585.html

> Asc

http://www.thescripts.com/forum/thread441566.html

> Left, Mid

http://www.thescripts.com/forum/thread246103.html

> Now, you're perfectly welcome to prefer the C# syntax. But in terms of
> functionality VB is not "identical" to C#... it's better.

We'll have to agree to disagree... :-)


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Just as i was about to be convinced to go with c#, CMoya's comments have
again put me back at 0-point :-)

Well, i am a part-time/casual developer. By profession i am a SysAdmin.
Developing is something i just like doing in my free time, and i create
small applications for internal use i our company, which are often
appreciated, since the developers are always working for customers.

The reason why i started with vb.net is because of the familiar syntax of
VBScript (Dim, if then else, for each etc etc...). I do have very good
knowlege og Javascript and a bit knowlege of J2EE as well. So, i dont really
think it will be much of trouble for me to switch to c#. Also because i'm
still a beginner with .NET.

But again, CMoya's comments sounds quite promising in favour of VB. Though
honestly, i didn't understand quite a few things he mentioned :-). But all
i'm looking for is "best" way to choose.

Thank you all for your helpful replies.

Regards.


"M. Ali Qureshi" <(E-Mail Removed)> wrote in message
news:726AB418-B792-4C73-A8A0-(E-Mail Removed)...
> Hi,
>
> I am a beginner in .NET. I have been coding in plain asp before, using
> VBScript, and now when i'm migrating to .NET, i obviously chosed VB.NET.
>
> But.... when i see code samples on net, they are mostly in C#, i also saw
> a post in this newsgroup where someone mentioned that it was a very
> "heated topic back in 2002 about VB.NET vs C#".
>
> So, my question is... what was the result of that topic?
> What is best to go for, VB.NET or C#? and why?
>
> Thanks and regards

Hi,

Just as i was about to be convinced to go with c#, CMoya's comments have
again put me back at 0-point :-)

Well, i am a part-time/casual developer. By profession i am a SysAdmin.
Developing is something i just like doing in my free time, and i create
small applications for internal use i our company, which are often
appreciated, since the full-time developers are always working for
customers.

The reason why i started with vb.net is because of the familiar syntax of
VBScript (Dim, if then else, for each etc etc...). I do have very good
knowlege og Javascript and a bit knowlege of J2EE as well. So, i dont really
think it will be much of trouble for me to switch to c#. Also because i'm
still a beginner with .NET.

But again, CMoya's comments sounds quite promising in favour of VB. Though
honestly, i didn't understand a few things he mentioned :-). But all i'm
looking for is "best" way to choose.

Thank you all for your helpful replies.

Regards.

"Mark Rae [MVP]" <(E-Mail Removed)> wrote in message
news:%23uLjs$(E-Mail Removed)...
> "M. Ali Qureshi" <(E-Mail Removed)> wrote in message
> news:726AB418-B792-4C73-A8A0-(E-Mail Removed)...
>
>> I am a beginner in .NET. I have been coding in plain ASP before, using
>> VBScript, and now when I'm migrating to .NET, I obviously chose VB.NET.
>
> Obviously??? You've clearly fallen into the trap that VB.NET is somehow an
> upgrade of Visual Basic and that ASP.NET is somehow an upgrade of ASP
> Classic. Apart from some peripheral syntactic similarities, nothing could
> be further from the truth. The reason, of course, is the .NET Framework...
>
> Since you're familiar with ASP Classic, you no doubt enjoy the comfort
> factor of Dim This As That, If...Then...Else...End If etc... But, since
> you're familiar with ASP Classic, you've almost certainly had some
> exposure to JavaScript, so basic C# syntax will already be totally
> understandable to you...
>
>> But.... when i see code samples on net, they are mostly in C#, i also saw
>> a post in this newsgroup where someone mentioned that it was a very
>> "heated topic back in 2002 about VB.NET vs C#".
>
> That was me...
>
>> So, my question is... what was the result of that topic?
>
> There was no result, because there is no right or wrong answer... Both
> languages are (almost) identical in terms of functionality - the only main
> advantage that C# had over VB.NET was support for unsafe code i.e.
> pointers. The reason that both languages are (almost) identical is because
> they both target the .NET Framework. At it most simplistic level, it
> really doesn't matter at all what .NET language you use - they are all
> identical...
>
>> What is best to go for, VB.NET or C#? and why?
>
> Both, and then decide which you prefer.
>
> It's my personal opinion that VB.NET is a totally unnecessary language,
> and it exists purely for reasons of marketing. Back in early 2002, outside
> of Microsoft and a tiny beta test community, there were no C# programmers
> at all. But there were millions and millions of VB programmers, and
> Microsoft weren't about to alienate them by releasing a new development
> suite with no flavour of Basic...
>
> Prior to .NET, I'd made my living almost exclusively with the various
> dialects of Basic right back as far as QuickBasic and on through VB for
> DOS, VB for Windows, VBScript, AccessBasic, WordBasic, VBA etc.
>
> But, after about a day with C#, I knew that I never wanted to write
> another line of Basic again! And, apart from one piece of work in 2004
> that I simply couldn't turn down, I never have...
>
> However, that's just my opinion...
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net

"M. Ali Qureshi" <(E-Mail Removed)> wrote in message
news:e$(E-Mail Removed)...

> But all I'm looking for is "best" way to choose.

Why do you actually have to choose at all...?


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

> Why do you actually have to choose at all...?
Maybe that was wrong choice of words. "Best way to begin" maybe :-)

Well, i have alot to learn in .NET yet, and if i go to c#, then syntax will
be yet another thing to learn. Besides, most of the samples online are in
c#, and by converting them always to VB for me will give me some knolege of
c# as well.

But since you are an MVP in asp.net. What would you suggest a beginner with
my background. VB or C# to begin learning?

Regards.

"Mark Rae [MVP]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> "M. Ali Qureshi" <(E-Mail Removed)> wrote in message
> news:e$(E-Mail Removed)...
>
>> But all I'm looking for is "best" way to choose.
>
> Why do you actually have to choose at all...?
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net

"M. Ali Qureshi" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...

>> Why do you actually have to choose at all...?
> Maybe that was wrong choice of words. "Best way to begin" maybe :-)

Fair enough.

> But since you are an MVP in asp.net. What would you suggest a beginner
> with my background. VB or C# to begin learning?

I would suggest you begin with C#, for no other reason that it will force
you to think in an object-orientated .NET way and prevent you from carrying
over any of the VBScript baggage...

I've known quite a few new (to .NET) developers who have begun with VB.NET
and then switched to C# - I've never known the reverse...

And, if ever you find yourself thinking "How would I have done this in ASP
Classic?", then have a five-minute break and approach the problem again from
the beginning... :-)


--
Mark Rae
ASP.NET MVP
http://www.markrae.net