vb.net vs c#

[Mark]

hi i would like you all to let me now some pro's and con's
between vb.net and c#
I want my company to get away from vb6 and move into 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 Rae]

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

Apart from the obvious difference in syntax, the two languages are pretty
much identical, apart from a few areas:

- C# supports pointers, VB.NET doesn't
- C# is case-sensitive, VB.NET (generally) isn't
- VB.NET permits sloppy coding (!) by turning off Option Strict

Plus a few minor other differences...

I want my company to get away from vb6 and move into c#

Ah, but that's a very different argument... You've posted in a C#
newsgroup, so most people here will applaud your wishes. However, even if
you have a huge investment in VB6, please don't let that influence your
choice of .NET language. One of the biggest mistakes people make is to
imagine that VB.NET is the next version of Visual Basic - it isn't - not
even close...

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

All of the above can be done equally well in C# or VB.NET. For virtually
every aspect of programming against the .NET Framework, the actual
programming language is irrelevant because they all compile down to the same
thing anyway...

I would advise you to take a modular approach based on the seven core
modules as outlined in the Microsoft Enterprise Library:
http://aspnet.4guysfromrolla.com/articles/022305-1.aspx, and develop
reusable base classes for each of these. I'd further advise you to start
with a database abstraction layer (DAL), because database connectivity is
pretty much fundamental to any business software development.

Doing this will not only give you a lot of exposure to the most important
areas of the .NET Framework, but it will also vastly simplify the rest of
your development tasks.

 

[Guest]

Apart from the obvious difference in syntax, the two languages are pretty
much identical, apart from a few areas:

- C# supports pointers, VB.NET doesn't
- C# is case-sensitive, VB.NET (generally) isn't
- VB.NET permits sloppy coding (!) by turning off Option Strict

Plus a few minor other differences...


Ah, but that's a very different argument... You've posted in a C#
newsgroup, so most people here will applaud your wishes. However, even if
you have a huge investment in VB6, please don't let that influence your
choice of .NET language. One of the biggest mistakes people make is to
imagine that VB.NET is the next version of Visual Basic - it isn't - not
even close...


All of the above can be done equally well in C# or VB.NET. For virtually
every aspect of programming against the .NET Framework, the actual
programming language is irrelevant because they all compile down to the same
thing anyway...

I would advise you to take a modular approach based on the seven core
modules as outlined in the Microsoft Enterprise Library:
http://aspnet.4guysfromrolla.com/articles/022305-1.aspx, and develop
reusable base classes for each of these. I'd further advise you to start
with a database abstraction layer (DAL), because database connectivity is
pretty much fundamental to any business software development.

Doing this will not only give you a lot of exposure to the most important
areas of the .NET Framework, but it will also vastly simplify the rest of
your development tasks.

Syntax or feature wise I don't think you can really argue that one is really
that much better than the other.

I personally think C# is a bit more popular in terms of documentation or at
least is easier to find code samples in C# than VB. This is a big C# selling
point for me.

Also, it seems that C# is a bit more popular when you do job searches. Your
company might have better luck finding C# developers than VB ones.

Jason Vermillion

 

[Guest]

This is a very old and tired subject which has been covered -- literally --
HUNDREDS of times in this and other newsgroups if you care to search.

VB.NET, while it can be considered a "first class" .NET citizen, is really
unnecessary to the .NET platform other than the fact that Microsoft didn't
want to leave 4 million classic VB programmers with no easy path to the .NET
platform (IMHO).
Peter

 

[Larry Lard]

This is a very old and tired subject which has been covered -- literally --
HUNDREDS of times in this and other newsgroups if you care to search.

VB.NET, while it can be considered a "first class" .NET citizen, is really
unnecessary to the .NET platform other than the fact that Microsoft didn't
want to leave 4 million classic VB programmers with no easy path to the .NET
platform (IMHO).
Peter

C# is 'unnecessary to the .NET platform' as well - the platform is
language-agnostic (which is quite an important part of its point).

Or would you say all but one of these:
<http://www.dotnetlanguages.net/DNL/Resources.aspx> are 'unnecessary' as
well?

 

[Guest]

Larry,
That is absolutely try in the strict interpretation of the comment. But, C#
was actually designed from the ground up as the target language for the .NET
platform, submitted to and ratified by ECMA. That's the point I was heading
at.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net

 

[Michael D. Ober]

I believe that large parts of both VS and the framework were written in C#.
I know that Microsoft.Practices.EnterpriseLibrary was written in C# - you
can download the source code.

Mike Ober.

 

[sloan]

Here is a 1.1 List:

http://groups.google.com/group/micr..."+regions+sloan&rnum=1&hl=en#2ec310d7b4b443b8

OR by this google search:
http://groups.google.com/groups/search?hl=en&ie=UTF-8&oe=UTF-8&q="Vb.net+does+not"+regions+sloan

...

Alot of people think going from vb6 to vb.net is easiest. I think "you
bring your bad habits with you".
C# forces a clear/clean "to OO" break.

Another good read:
http://www.google.com/search?hl=en&q="Not+Another+C#+Versus+VB+Article"
http://www.codeproject.com/dotnet/CSharpVersusVB.asp

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,


| hi i would like you all to let me now some pro's and con's
| between vb.net and c#
| I want my company to get away from vb6 and move into c#
| we do alot of online transactions mssql2005
| back end services, processing ,email, fpt, vpn etc.
| and front end web reporting, ftp, information pages

In short there are not too many differences. Both use the same framework.

Use the one that you like the most

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,


message | Larry,
| That is absolutely try in the strict interpretation of the comment. But,
C#
| was actually designed from the ground up as the target language for the
..NET
| platform, submitted to and ratified by ECMA. That's the point I was
heading
| at.
| Peter

I read somewhere that C# was for those who are too machos for Vb.net and too
weak for C++

Jokes apart I like the syntax that's why I use it. In completely honestly I
do not remember to have used a C# only feature ever.

 

[Mark]

Well thanks all for you responses......
Ive done c,c++ the most of my last few years was
using visual objects (ca-vo) wich is completly OOP and native compiler...but
time to go to net....
I personally like c#......Ive Never liked VB....

again Thanks for all the responses....
Mark

 

[Willy Denoyette [MVP]]

Well thanks all for you responses......
Ive done c,c++ the most of my last few years was

If that's the case you might take a look at C++/CLI, another powerfull .NET language.

Willy.

 

[Larry Lard]

Hi,


message | Larry,
| That is absolutely try in the strict interpretation of the comment. But,
C#
| was actually designed from the ground up as the target language for the
..NET
| platform, submitted to and ratified by ECMA. That's the point I was
heading
| at.
| Peter

I read somewhere that C# was for those who are too machos for Vb.net and too
weak for C++

I'm definitely remembering that one

Jokes apart I like the syntax that's why I use it. In completely honestly I
do not remember to have used a C# only feature ever.

Anonymous delegates make some things very nice, and I can't see how you
could readily (and 'nicely') express them in a Basic-like syntax...

 

[Dan Reber]

If your company is making software to sell and the languages have mostly the
same functionality then you may want to choose a language based on the
outside perception. We chose to port our large VB6 application to C#
because it "sounds" better than Visual Basic to non-technical people.
Again, this is only if you do not have a preference to a language. I
personally prefer the case-sensitivity and syntax structure of C#, it makes
it easier to read, so I am glad that we went with it.

Dan

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

| Ignacio Machin ( .NET/ C# MVP ) wrote:

|
| Anonymous delegates make some things very nice, and I can't see how you
| could readily (and 'nicely') express them in a Basic-like syntax...

I do not know the answer to that question, I haven't worked in VB.net for at
least a year and beside, I totally hate VB syntax.

I totally agree with Peter than MS was forced to create "something" and
called it VB something. Otherwise the VB folks would complain like crazy.

 

[Mark Rae]

I do not know the answer to that question, I haven't worked in VB.net for
at
least a year and beside, I totally hate VB syntax.
Likewise.

I totally agree with Peter than MS was forced to create "something" and
called it VB something. Otherwise the VB folks would complain like crazy.

Yes but, playing devil's advocate here, imagine if VB.NET had been the top
..NET language and C# merely a sop to the VC++ community...;-)

 

[Dave P]

I hated the basic language even back in the day...many moons ago in
college....would not program with it then or under windows....but thats
me....

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

| "Ignacio Machin ( .NET/ C# MVP )" <machin TA laceupsolutions.com> wrote in
| message |
| > I do not know the answer to that question, I haven't worked in VB.net
for
| > at
| > least a year and beside, I totally hate VB syntax.
|
| Likewise.
|
| > I totally agree with Peter than MS was forced to create "something" and
| > called it VB something. Otherwise the VB folks would complain like
crazy.
|
| Yes but, playing devil's advocate here, imagine if VB.NET had been the top
| .NET language and C# merely a sop to the VC++ community...;-)
|

That's is a good one

Yes, I think that it could had been like that. But IMO this would had given
the impression of a less than powerful and maybe less profesional framework.
cause everybody knows that VB has not half the power than C++.
Unfortunately C++ is very difficult to learn and exploit. so there is Java,
that was like the "perfect" compromise. So MS basically create a Java
competitor.