VB .Net vs. C#

  • Thread starter Thread starter Guest
  • Start date Start date
virtually none. Both use the same framework. Use what you or your
developers like the best.
 
Just put it in Google...there's a ton out there. However, by and large, if
you code VB.NET with Option Strict on, the main benefit of C# is the ability
to use unsafe code blocks... On VB.NET's side, it's got to be the most user
friendly and pleasant to use environment ever made.

HTH,

Bill
 
The main reason I like VB over C# has more to do with Visual Studio than the
actual languages. Inside Visual Studio, VB has full background compilation
so you get immediate sytnax checking and somewhat better Intellisense while
C# requires a build to provide this feedback.

Other than that I don't think one has any real advantage over the other. I
do know they're both head-and-shoulders better than any other tool I've
used.
 
Rob Windsor said:
Other than that I don't think one has any real advantage over the other. I
do know they're both head-and-shoulders better than any other tool I've
used.
Click to expand...

I support C# over VB almost religiously to the point of being silly. But
this have more to do with my absolute deep held truth that 'Visual Basic
Sucks So Hard It Bends Light'. =)

If I have to put brains into the mix, we have ditched VB for C#, as C# is
more close to Java and our shop does a lot of work in Java.

But I have found a case where VB.NET is far more useful than C# and that's
when you try to work with COM-interop in .NET. As C# doesn't sport optional
parameters, doing stuff like office-automation in C# is somewhat annyoing
with all the Type.Missing all over the source.

Hence, the next time I have anything to do with a COM-stack that relies
heavily on optional parameters, I will choose VB.NET for this task, or
perhaps Delphi.NET.

- Michael S
 
Back
Top