Book on differences between VB and C# .NET?

  • Thread starter Thread starter Brett
  • Start date Start date
B

Brett

Are there any books that mainly discuss differences between VB.NET and
C#.NET? Possibly situations where you would specifically need/want to use
one language over another.

Thanks,
Brett
 
I'm looking for something more conceptionally. Not so much that one uses
ME and the other uses THIS. As I mentioned, I'd like to see (explanations
of) several example projects of why some one would "need" to use C# or
VB.NET and vice versa.

Thanks,
Brett

"AMALORPAVANATHAN YAGULASAMY(AMAL)"
 
Basically, it seems these two languages are the same with very minor
differences, mainly in the syntax domain. To accomplish something in one,
is to accomplish the same thing in the other.
 
Brett,

"The existing experience of a programmer far outweighs the small
differences between the two languages" (MS white paper).

I don't think you are going to find real-world situations where one
language is preferable to the other, as all things being equal they
cover exactly the same ground. What you will find, is a VB developer
getting to grips with the .NET framework quicker with VB.NET that
C#.NET, and a C++/Java developer doing the same with C#.NET.
Nick
 
Nick said:
Brett,

"The existing experience of a programmer far outweighs the small
differences between the two languages" (MS white paper).

I don't think you are going to find real-world situations where one
language is preferable to the other, as all things being equal they
cover exactly the same ground. What you will find, is a VB developer
getting to grips with the .NET framework quicker with VB.NET that
C#.NET, and a C++/Java developer doing the same with C#.NET.
Click to expand...

At the company I worked for when .NET was released, one of the minor
reasons we decided to take the C# route rather than the VB route was
that we still had to maintain VB6 systems, and working in two distinct
languages seemed easier than working in two VB dialects.
 
Steve Walker said:
At the company I worked for when .NET was released, one of the minor
reasons we decided to take the C# route rather than the VB route was that
we still had to maintain VB6 systems, and working in two distinct
languages seemed easier than working in two VB dialects.
Click to expand...

Seems like it would be the other way around. Can you elaborate?

Thanks,
Brett
 
good point Steve...I wonder how many dev teams took such a sensible
route? not many Im guessing...
 
Back
Top