VB Programmer looking to move to C#
-
I've been programming w/ VB/VB.Net for a few years now and have been thinking of switching over to C#. For my job no one cares what language I use, so it's just something I've been thinking about and maybe it'll make me more marketable later if needed. So my question is for those that work in both, what are some of the benefits of C# over VB.Net? I'm really not interested in a "my language is better than your language" war, just reasons why someone who uses both would choose c# over VB or VB over c# for a particular project. Thanks for your input Al
-
I've been programming w/ VB/VB.Net for a few years now and have been thinking of switching over to C#. For my job no one cares what language I use, so it's just something I've been thinking about and maybe it'll make me more marketable later if needed. So my question is for those that work in both, what are some of the benefits of C# over VB.Net? I'm really not interested in a "my language is better than your language" war, just reasons why someone who uses both would choose c# over VB or VB over c# for a particular project. Thanks for your input Al
C# is probably more popular than VB .NET and is a bit better supported in the .NET environment than C#, at least in the 2003 version. That's about it. I did read something recently though suggesting that VB .NET is has a slight edge over C# when using Visual Studio Tools for Office. But IMO whichever language you go for you should still be able to at least read C# code. Kevin
-
C# is probably more popular than VB .NET and is a bit better supported in the .NET environment than C#, at least in the 2003 version. That's about it. I did read something recently though suggesting that VB .NET is has a slight edge over C# when using Visual Studio Tools for Office. But IMO whichever language you go for you should still be able to at least read C# code. Kevin
Kevin McFarlane wrote: I did read something recently though suggesting that VB .NET is has a slight edge over C# when using Visual Studio Tools for Office. AIUI The potential advantage is with any com object. c# doesn't support optional parameters which means that directly using com objects that do take them can get ugly since a 'placeholder' type parameter needs passed for each one. The office interop classes are noteworthy in having a huge number of almost never used parameters which would make for really nasty coding if used directly. Ofc there's no reason you can't write a c# wrapper to hide the uglyness and call it instead.
-
C# is probably more popular than VB .NET and is a bit better supported in the .NET environment than C#, at least in the 2003 version. That's about it. I did read something recently though suggesting that VB .NET is has a slight edge over C# when using Visual Studio Tools for Office. But IMO whichever language you go for you should still be able to at least read C# code. Kevin
I can read and write it (although at a much slower rate) but don't feel comfortable with it. Before with "classic" ASP/VB you could create objects but not achieve real OOP. As I get more into .Net I would like to take advantage of OOP and it seems more difficult learning it with VB.Net. I read about Final, Static and Abstract in C# or Java and other OO languages but have to translate them into things like Shared, Overridable, or MustImplement. I really wish the VB.Net Team at Microsoft would have used what seems to me as standard terminology. I actually thought VB was the better supported language as it's intellisense seems better with forcing proper indentation and such. Also I really like that VB has the background compiler. I do like that C# points out unused variables and provides warnings not just errors. It also seems that searching Yahoo or Google for an code snippet will yield FAR more C# results than VB. Can I ask why you think C# is the better supported of the two? Al
-
I can read and write it (although at a much slower rate) but don't feel comfortable with it. Before with "classic" ASP/VB you could create objects but not achieve real OOP. As I get more into .Net I would like to take advantage of OOP and it seems more difficult learning it with VB.Net. I read about Final, Static and Abstract in C# or Java and other OO languages but have to translate them into things like Shared, Overridable, or MustImplement. I really wish the VB.Net Team at Microsoft would have used what seems to me as standard terminology. I actually thought VB was the better supported language as it's intellisense seems better with forcing proper indentation and such. Also I really like that VB has the background compiler. I do like that C# points out unused variables and provides warnings not just errors. It also seems that searching Yahoo or Google for an code snippet will yield FAR more C# results than VB. Can I ask why you think C# is the better supported of the two? Al
Al Ortega wrote: I really wish the VB.Net Team at Microsoft would have used what seems to me as standard terminology. Actually I think some of the VB terminology is better than the “standard” terminology. But we do tend to gravitate towards standards, whether those standards make sense or not. Of OO languages Eiffel tends to have the clearest terminology. Al Ortega wrote: I actually thought VB was the better supported language as it's intellisense seems better with forcing proper indentation and such. Well, one of the worst aspects of the C-family languages is the code layout wars over curly brace placement! So VB is better in that respect at least. But I really meant with respect to language and environment features rather than usability – e.g., built-in support for XML code comments, operator overloading, the using keyword for convenient disposing of resources. However, these differences have narrowed in VS 2005, as VB has got most of these features too. Al Ortega wrote: It also seems that searching Yahoo or Google for an code snippet will yield FAR more C# results than VB. That’s one of my reasons for saying that you should at least be able to read C#. That way you can comfortably translate C# samples into VB .NET. There are tools to do this but you need to be able to fill in any gaps they leave. (I also think that C#ers should be able to read VB, though not to the same extent.) BTW, I’m not one of those C-family developers who hate VB. I’ve used both classic VB, in most of its variants, and VB .NET. I can live with them, even though I’m mostly doing C# now. This is because given my C++ background I’m perceived to be a C-family developer. Kevin
-
Al Ortega wrote: I really wish the VB.Net Team at Microsoft would have used what seems to me as standard terminology. Actually I think some of the VB terminology is better than the “standard” terminology. But we do tend to gravitate towards standards, whether those standards make sense or not. Of OO languages Eiffel tends to have the clearest terminology. Al Ortega wrote: I actually thought VB was the better supported language as it's intellisense seems better with forcing proper indentation and such. Well, one of the worst aspects of the C-family languages is the code layout wars over curly brace placement! So VB is better in that respect at least. But I really meant with respect to language and environment features rather than usability – e.g., built-in support for XML code comments, operator overloading, the using keyword for convenient disposing of resources. However, these differences have narrowed in VS 2005, as VB has got most of these features too. Al Ortega wrote: It also seems that searching Yahoo or Google for an code snippet will yield FAR more C# results than VB. That’s one of my reasons for saying that you should at least be able to read C#. That way you can comfortably translate C# samples into VB .NET. There are tools to do this but you need to be able to fill in any gaps they leave. (I also think that C#ers should be able to read VB, though not to the same extent.) BTW, I’m not one of those C-family developers who hate VB. I’ve used both classic VB, in most of its variants, and VB .NET. I can live with them, even though I’m mostly doing C# now. This is because given my C++ background I’m perceived to be a C-family developer. Kevin
hi my name is seshu i am use vb60 i have lean basic in vb now c# is like vb me be it easy to lean c# and my email id netmseshu@yahoo.co.in
-
hi my name is seshu i am use vb60 i have lean basic in vb now c# is like vb me be it easy to lean c# and my email id netmseshu@yahoo.co.in
A lot of VB programmers have moved to C# with no problems. The guy who sits next to me at work is an ex-VB 6 programmer and he's fine using C#. Certain aspects of C# will already be familiar to you, e.g., properties. The main learning-curve is the .NET framework itself, and maybe OO concepts, if you weren't already familiar with them. Switching syntax is easy. Kevin