VB .Net or C#? Why choose one over the other?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

IF you choose C#...it's can almost port seamlessly to Java

HUGE ADVANTAGE........

Also, if you have Java, you can easily port that to C#......

And if you have JavaScript...that too can be easily ported to C#

BIG Advantage......
 
VB.NET is much more different from VB6 than VB.NET and C# are. There is not
'real' reason. If you have a bunch of C/Java developers, the learning curve
will be shorter with C#. If you have VB programmers and they are real
programmers (See Option Strict ON) you'll get the same results. VB is more
verbose....C# is a ball buster with case sensitivity.

If they are even asking, they don't need to go to .NET. IL, which it all
compiles to in the end is almost identical. See Dan Appleman's ebook on the
subject, he covers it in depth.

The managed environment is a new paradigm (If I sound like a KPMG
consultant, please forgive me) and the differences between C# and VB.Net are
trivial. Any top notch VB.NET programmer can be a top notch C# programmer
in under two or three weeks and vice versa. Any Top notch VB6 or C++
programmer can be a top notch .NET developer, but it'll take a few more
weeks.

HTH

Bill
 
VM.... To a beginer I recommend C# simply because it uses the "C"
syntax. This makes it easier to switch between C++, C#, Java,
JavaScript,
Objective-C and C projects.

Regards,
Jeff
The reason I chose C# is because it's somewhat
Click to expand...
similar to C (and I've never liked VB6).
I've had clients ask me that but I don't have a definite answer.<
 
Although I program in C# and all of the projects I work on are in C#, I was
just wondering why someone would choose VB .Net or C#.
Since VB .Net is as similar to VB6 as C# is toVB6, why would a programmer
choose one over the other? The reason I chose C# is because it's somewhat
similar to C (and I've never liked VB6).
I've had clients ask me that but I don't have a definite answer. Any links
with info would be greatly appreciated.

Thanks.
 
And if you don't want to wait all day for a Java Applet to run or don't want
well performing .NET apps porting to Java....

I primarily write in C#, but none of your reasons ever crossed my mind. J#,
which is almost as lame as Pure Java ports identically depending on the OS.
But dude didn't even mention Java........so why do you bring it up?
 
If you want "world-class" ide, use vb.net (I say this only with envy of the
vb.net ide as I tend to write more c# code). As was said at a recent dotnet
user's group meeting I attended in Dallas, Texas:
"All .Net languages are created equal" -- "But not all IDE's are created
equal"

For example, you seldom have to type out an enum name in vb.net, it knows
automagically. It compiles as you code and highlights errors (which is a lot
better than the vb6 where it wouldn't let you leave a line with an error -
very annoying, but also an advantage over C# because errors as you code are
easily visible in the Tasks box. And if there are no errors in the Tasks box
as you code, then you're pretty much guaranteed that it will compile fine).
I could name many other exmaples, including properties, if / end if, event
handling for windows / web forms, implementing methods of parent classes,
etc.

However, there are some things you can do in C# that you cannot do in
vb.net. For example, if you want/need operator overloading or unsafe code
(pointers) then c# is the way to go. So far, I've only ever overloaded ==
and !=, and could have done just as well with .Equals() had that been my
only option. But some projects (math-oriented especially) would benefit from
the overloading. And if you (like me) have a C++ and/or Java background, the
{}'s will probably "feel" better than If__ End If, Sub__ End Sub, etc.

I admit my list above is 99% about the developer - not necessarily the
client. I can't think of too many things that would actually affect a
client, and I think that's because the end result will be pretty much the
same to them.
 
Back
Top