Is there a good reason to choose one over the other? I
personally prefer C# since my background is in C++ and
Java.
Basically, the people that program in C++ or Java like C# b/c they like
syntax that is clean and not verbose. Hearing the words "Visual Basic"
automatically makes them repulsed and wanting to vomit. :-)
The people using VB.NET like the fact that the language has some
improvements to the IDE so that the VB6 programmers find it easy to use.
Also, I talked to a MS Rep at a conference and he said that MS is planning a
lot more improvements to make VB.NET easier and these changes won't be
implemented in C#. He didn't expand on what those changes are going to be.
This makes me want to be a fly on the wall to see what they have up their
sleeves....
A lot of people don't think it matters which you choose. Both languages are
soooo similar that once you learn one its easy to learn the other
(especially with my book!). The hard part comes with learning the Framework.
My opinion: If you know C++, learn C#. If you know VB6, learn VB.NET. You
can argue all day which is better, but using what you are already familiar
with makes the task so much easier. Once you understand how the framework
works it is TRIVIAL to learn the other language.
Brian Bischof, CPA, MCSD, MCT
"The .NET Languages: A Quick Translation Guide"
www.bischofsystems.com/csharp.asp
"Rippah" <ar...@cfl.rr.com> wrote in message
news:e71201c1ab6e$48998f20$a4e62ecf@tkmsftngxa06...
/Johan
"Rippah" <ar...@cfl.rr.com> wrote in message
news:e71201c1ab6e$48998f20$a4e62ecf@tkmsftngxa06...
Actually there are a few things, but the question remains as to whether or
not it is trivial.
C# can use unchecked math for specific sections, which makes calculations
faster. However this opens the possibility of logic errors due to overflows,
so I would never use it.
Gunnerson did an article on unsafe sections which showed that they can be
faster. Again, the slight performance advantage was not enough to make me
want to deal with the headaches involved in using it.
--
Jonathan Allen
.Net Wish List Site: http://jonathan.cloverlink.com/
"Rippah" <ar...@cfl.rr.com> wrote in message
news:e71201c1ab6e$48998f20$a4e62ecf@tkmsftngxa06...
>And, as far as I see it
>you can do about 99% of what you can do in C# in VB.NET.
You can look at it the other way around and say the same thing about
VB.NET. There are things you can do in VB.NET that can't be done in
C#.
>but, you cant do unmanaged coding in VB.NET.
Neither can you do it in C#.
>Whan ot
>comes to the "VB Coding is for newbies" issue, my opinion is that its pure
>bullshit...
It is for newbies *too*. That's one of it's strengths.
Mattias
===
Mattias Sjögren (VB MVP)
mattias @ mvps.org
http://www.msjogren.net/dotnet/
Cheers,
John
"Rippah" <ar...@cfl.rr.com> wrote in message
news:e71201c1ab6e$48998f20$a4e62ecf@tkmsftngxa06...
"Mattias Sjögren" <mattias.don...@mvps.org> wrote in message
news:#7X4V84qBHA.1864@tkmsftngp04...
Unmanaged code is code that doesn't run on the CLR and isn't compiled as IL
code.
VB.Net, C#, and JScript.Net can only produce managed code.
Since C# can use pointers, it is said to have the ability to produce unsafe
code. But as mentioned before, pointers are just one of many ways to render
your code unsafe.
C++ can produce both managed and unmanaged code. But since pointers are
integral in C++, it is always considered to be unsafe code.
--
Jonathan Allen
.Net Wish List Site: http://jonathan.cloverlink.com/
"Smurf" <eme...@optushome.com.au> wrote in message
news:Og#8abFrBHA.2432@tkmsftngp07...