Vb.Net or C#.Net

[Kamal Ahmed]

Hi guys.....

I have 2 options to develop a Asp.Net Portal either using VB.Net or C#.Net.
What is difference between these two languages. and what is edge of
develoing in C# because mostly companies require developing in C#.Net. And
what are drawbacks in VB.Net that differs it with C#.Net ???
What option should I choose???.

TIA

 

[Grant Merwitz]

Your about to start a debate.

A die hard c# programmer will argue C# is better, where VB programmers the
opposite.

They are both efficient, and both do the job.
NONE IS BETTER THAN THE OTHER.
So, It doesn't matter which option you choose.

I personally prefer c#, but don't claim its any better

 

[Onin Tayson]

Yep... this usually starts a debate but I suggest you go with which language
you are more comfortable using. I started with VB but now I'm using C# and
it's not that hard switching from one language to the other. You'll be
programming against the framework most of the time so you should understand
what the framework is capable of doing, any language will suffice... ;-)

 

[tom pester]

Although there is no difference in what each language can express (you can
almost convert C# to VB and vice versa with a program) there are some practical
consequences

- I have the feeling more code samples (of good quality) are done in C#
- If you use Visual studio than the background copilition if you use VB.NET
can be a) quite helpful b) a big nuissance if your project is getting large
My subjective feeling is that programming C# in VS.NET is more responsive
- There are compilers for C# on other platforms (unix/mono project fe.)
- VB.NET doesn't force the programmer into being presice when it comes to
type. Whether this is good for your needs I don't know but it catches some
errors early in the dev process.

If you start from scratch and want to specialize in a language I would advice
C# cause it also resembles other languages that you can come in contact with
in the future (C++,Jave).
I think its also easier to learn VB.NET once you know C# than vica versa
cause in C# asks more discipline from the programmer.

That being said I started with VB.NET and try to spend my time 50/50 between
the 2 languages just to keep the syntax in my fingers.


Cheers,
Tom Pester

 

[logan]

I find that I do less typing when using C# over VB.Net.
Other than that MS created both languages equal.

 

[Grant Merwitz]

If only god had done the same with man

I find that I do less typing when using C# over VB.Net.
Other than that MS created both languages equal.

 

[Kevin Spencer]

The only difference between the 2 languages is syntax. However, I would
caution you, if you are a VB or VBScript programmer, you can easily get into
trouble treating VB.Net like VB or VBScript. It is not either, even though
it looks like both.

Whichever language you use, apply good OOP principles to what you do, and
you will do well.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Everybody picks their nose,
But some people are better at hiding it.

 

[Karl Seguin]

I'll add my $0.02 ...I used to program in VB.Net and thought it made it too
easy to write bad code, because of it's legacy support for on error resume
next (instead of forcing try/catch) and it's abilality to be late-bound.
I've since changed my mind and decided that given any language, a shitty
programmer would still write shitty code. I program in C# now, but I'd
strongly (and often do) stand by VB.Net and defend it.

That said, it does look like future releases (as soon as 2.0) are starting
to see greater differences. Better nullable type support in C#, refactoring
when it ships, yield...and VB.Net also has new stuff, but different. It's
all fairly minor stuff, but certainly worth keeping a close eye on it.

All in all, I'd strongly agree that you follow people's advice and use
whatever's more natural...but if that's VB.Net, please don't use on error
resume next and consider enabling option strict

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/ - New and Improved (yes, the popup is
annoying)
http://www.openmymind.net/faq.aspx - unofficial newsgroup FAQ (more to
come!)

 

[Kevin Spencer]

All in all, I'd strongly agree that you follow people's advice and use

whatever's more natural...but if that's VB.Net, please don't use on error
resume next and consider enabling option strict

Well, as long as we're delving into the possible pitfalls of using VB.Net, I
would add that option strict is almost indispensible, and that using Modules
is a very bad idea, in general. In fact, using Shared (static) scope is
dangerous in OOP, and should be avoided unless one understands all of the
ramifications of it. That said, Shared (static) scope is quite useful, and
there are definitely times when it can provide a great degree of
optimization in an application.

Again, understanding OOP is the key to successful .Net development in any
language. Since C# became so popular, I have seen far too many abuses of it
as well, although they are a littl harder to produce.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Everybody picks their nose,
But some people are better at hiding it.

 

[Grant Merwitz]

Sometimes i wonder if i ever truly will understand OOP.

As much as i think i know (aced my way through University in OOP - didn't
help shit)
I always have more to learn!

 

[Kevin Spencer]

I always have more to learn!

Anyone who thinks they don't is an idiot!

--

Kevin Spencer
Microsoft MVP
..Net Developer
Everybody picks their nose,
But some people are better at hiding it.

 

[Steve C. Orr [MVP, MCSD]]

VB.NET rules!

 

[tom pester]

I failed to come up with a better argument. Damn

Cheers,
Tom Pester

 

[Kevin Spencer]

Very funny, Steve. I'm not sure everyone is cognizant of your sense of
humor, however.

To those of you from Rio Linda, California: Steve is NOT trying to start an
argument!

--
;-),

Kevin Spencer
Microsoft MVP
..Net Developer
Everybody picks their nose,
But some people are better at hiding it.