VB.net or C#.net

[jonabyte]

Hello,

I am wondering what the basic reasons for choosing one language over another, specifically vb.net or c#.net. Can someone tell me what one has that the other doesn't. I have made some usable apps in vb.net, and explored c#, but I am just wondering why I would make an app in c# if vb does the same thing.
I am not looking for why one is better than the other or to start a flame war just advantages, etc.
Apologies if this has been covered to death.

j

[techgnome]

Bottom line - presonal preference....

-tg

[jonabyte]

Do you mind expanding a little, I do know what you mean but for which lang?
I prefer to use vb since I have been using that lang for many many years. Same for you??

[gigemboy]

The two are basically fraternal twins. They use the same type of objects and have the same kind of structure. One just has a different syntax than the other. One thing that C# has that I hear often is the ability to use pointers, which VB.NET does not have... (although I haven't ever used pointers before, so I cannot give advice as to what they are and what the uses are ) That is why "preference" was stated, as it is really just a matter as to what syntax you prefer to program in.

For me, I love how verbose vb.net is, and how easily the code is to read and understand (almost self-documenting, as you can understand what is going on by just reading the code and methods), thus, I use it over C#.

[RobDog888]

Here are a couple of threads where it was discussed in depth.

http://www.vbforums.com/showthread.php?t=379274
http://www.vbforums.com/showthread.php?t=367985

[jonabyte]

thanks for the repsonses and links, I'll probably just stick with vb for now.

Another question, is it worth the upgrade to vb.net 2005? I am using vb.net 2003 without any problems, so I should probably just stick with it.

Thanks again.

[Hack]

thanks for the repsonses and links, I'll probably just stick with vb for now.

Another question, is it worth the upgrade to vb.net 2005? I am using vb.net 2003 without any problems, so I should probably just stick with it.

Thanks again.

Upgrading for the sake of upgrading isn't always advisable, but if you are going to get some bang for your buck, the upgrading makes sense.

This is a difficult question to answer because I don't know what your particular needs are. My suggestion would be to research VS2005 (Lord knows there is enough information on it out there), and make a determination as to whether you would benefit from upgrading. There may be features of 2005, that are not in 2003, that you would find very useful. On the other hand, there may not be.