VB vs C#

  • Thread starter Thread starter Mark
  • Start date Start date
M

Mark

hi i would like you all to let me now some pro's and con's
between vb.net and c#

We do alot of online transactions mssql2005
back end services, processing ,email, fpt, vpn etc.
and front end web reporting, ftp, information pages

tia
mark
 
Mark said:
hi i would like you all to let me now some pro's and con's
between vb.net and c#
Click to expand...

See the thread with subject "Fw: VB.NET vs C#.NET (and 1.1 vs 3.0)" from a
few days back, that should answer your question.
 
hi i would like you all to let me now some pro's and con's
between vb.net and c#

We do alot of online transactions mssql2005
back end services, processing ,email, fpt, vpn etc.
and front end web reporting, ftp, information pages

tia
mark
Click to expand...

Please search the archives for this question on google groups - it has
been covered literally hundreds of times.

Here's the search results for your subject line:

http://groups.google.com/group/micr...nguages.vb&q=+VB+vs+C#&qt_g=Search+this+group
http://groups.google.com/group/micr...ges.csharp&q=+VB+vs+C#&qt_g=Search+this+group

Thanks,

Seth Rowe
 
Go search the VB and C# newsgroups for this. It has been discussed
exhaustively at least twice in the last month in both groups.

VB people thing VB is easier to read and should be used instead of C#.

C# people look down on VB people because VB is easier to read and the old
versions of VB made it easier to be a sloppier programmer because of loose
typing and because that's how they are.

Bottom line: There's some stuff that's best in one language or the other,
but it's very, very minimal. For the most part, they are very, very close.
All of the .Net Framework classes work the same in both languages.

It's like picking between French and Spanish.

Robin S.
Ts'i mahnu uterna ot twan ot geifur hingts uto.
-----------------------------------------------
 
It's like picking between French and Spanish.

Spanish, because it's less prissy sounding.

Bob Lehmann
 
I didn't say *which* was French and *which* was Spanish. Now I will declare
that VB is Spanish, and C# is French. After all, C# is a lot ruder than VB.
At least, to tourists. ;-)

Robin S.
Ts'i mahnu uterna ot twan ot geifur hingts uto.
-----------------------------------------------
 
Well for previous VB6 proggers i would definedly say move to VB.Net , buy
the Balena books ( programming microsoft visual basic series i would still
buy the 2003 and 2005 version )
as they have special attention for VB6 proggers an in a few days you wil at
least feel at home :-)

If you would like to earn more money , or beat yourself on the chest that
you are a C style progger well then go for C# you wil now have a much
higher learning curve but once you code in C# and with your VB6 background
VB.Net is peanuts , on the other hand when you code in VB.net with option
strict on and option explicit on ( wich i would highly recomend you do )
and try to use as much as possible FCL code instead of the language
enhancement code that VB provides ( len() vs string.length etc etc ) well
then reading and writing C# code is also peanuts

So my recomendation previous language derived from Algol ( C++ , Delphi )
go for C#
previous language derived from Fortran
( Cobol , Basic ) go for VB.Net


As you see this hole discussion goes back to the start of programming , and
wich one is better ??? well it is probably the same thing as saying that
Ferrari is bether as Lamborghini and should be seen as a personal
preference .

regards

Michel Posseth (
Can code in both but just prefer VB as it is my native tongue :-) )
 
Michel,

Just that I saw it, change your Fortran advice to the C# part. Fortran was a
kind of less complex language in the same area as Algol. Both based on
algebraic way of describing processes.

Cobol is surely not derived from Fortran, there have been heavier
discussiong between Fortan and Cobol people than there ever can be between C
and VB types of languages.

Cor
 
Well maybe the hole derived from is wrong for the basic part :-( as also
basic goes back to 1963 ,,, however fact is that classic Basic looks a lot
like Fortran , but it seems it has also inherited from ALGOL

maybe i should have said

spoken notation ( wich COBOL also fits ) against scientific notation

By the way i just saw on a history path list that COBOL has it`s own line
without anny branches

regards


Michel
 
Michael,

If you see what I wrote beneath can be typical Cobol sentence than you will
probably understand that it has nothing to do with Fortran. (I do not know
exact the sentax anymore)

If leeftijd in JanPeterBalkenende < leeftijd in WouterBos then
Sort Beleeftheidstermen
MoetGebruikenBeleeftheidsterm in JanPeterBalkenende = true.

Often I have seen in those days people proofing that Cobol was slow, once I
saw it while a guy had translated his Fortran Sort routine to Cobol. He had
used the Fortran Keywords 1 to 1 to Cobol. He did not know that for sort
there was an inbuild routine and (on the machine I was using then) very
fast.

leeftijd in JanPeterBalkenende we write now as
JanPeterBalkenende.leeftijd

The line delimiter was the dot. And that was the main reason for errors.

Although you will think it does, had the starting Basic nothing to do with
Cobol. It was disliked by Cobol programmers. As you see got the later Basic
in my idea lots of ellements from Cobol.

Cor
 
Michel Posseth said:
Well maybe the hole derived from is wrong for the basic part :-( as also
basic goes back to 1963 ,,, however fact is that classic Basic looks a
lot like Fortran , but it seems it has also inherited from ALGOL
Click to expand...

IIRC BASIC has been invented as an alternative to FORTRAN which has been
used to teach programming.
 
Back
Top