VB vs. C#
-
just wondering: is there anything that VB.NET can do that C# cannot? i noticed some of the Enterprise Library was written in C#, which is why i can't use it. which angers me, but i guess i'll just have to spend the $600 to... anyway, back to the question. is there anything one can do with VB that one can't do with C# or vice versa?
-
just wondering: is there anything that VB.NET can do that C# cannot? i noticed some of the Enterprise Library was written in C#, which is why i can't use it. which angers me, but i guess i'll just have to spend the $600 to... anyway, back to the question. is there anything one can do with VB that one can't do with C# or vice versa?
Nope. They both target the exact same platform. There are coding issues that apply to one but not the other, but in the end, it's just a matter of preference. For example, C# doesn't support optional parameters in method calls, where as VB.NET does. On the other hand, VB.NET doesn't support pointers and "unsafe" code, where as C# does. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
just wondering: is there anything that VB.NET can do that C# cannot? i noticed some of the Enterprise Library was written in C#, which is why i can't use it. which angers me, but i guess i'll just have to spend the $600 to... anyway, back to the question. is there anything one can do with VB that one can't do with C# or vice versa?
VB.Net and C# are arguably becomming more and more different over time (Will the idea of a '.Net developer' soon die?[^]. In my opinion, each language has their own unique features that allow you to solve problems in different ways programmatically. One language might have a particular feature that will allow you to solve a problem in a more elegant way, or in a way that requires less time. However, I'd argue that for many projects the differences are insignificant. In terms of meeting a user's requirements or coding out an object model from a class diagram, there's nothing VB.Net does that C# can't, and vice-versa. In this case, the decision might have more to do with developer skills and which language the developer(s) is(are) more comfortable with. Michael Hodnick www.kindohm.com
-
VB.Net and C# are arguably becomming more and more different over time (Will the idea of a '.Net developer' soon die?[^]. In my opinion, each language has their own unique features that allow you to solve problems in different ways programmatically. One language might have a particular feature that will allow you to solve a problem in a more elegant way, or in a way that requires less time. However, I'd argue that for many projects the differences are insignificant. In terms of meeting a user's requirements or coding out an object model from a class diagram, there's nothing VB.Net does that C# can't, and vice-versa. In this case, the decision might have more to do with developer skills and which language the developer(s) is(are) more comfortable with. Michael Hodnick www.kindohm.com
Mike Hodnick wrote: there's nothing VB.Net does that C# can't, and vice-versa. Whoa! Don't let Christian see you posting this! :laugh: RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
VB.Net and C# are arguably becomming more and more different over time (Will the idea of a '.Net developer' soon die?[^]. In my opinion, each language has their own unique features that allow you to solve problems in different ways programmatically. One language might have a particular feature that will allow you to solve a problem in a more elegant way, or in a way that requires less time. However, I'd argue that for many projects the differences are insignificant. In terms of meeting a user's requirements or coding out an object model from a class diagram, there's nothing VB.Net does that C# can't, and vice-versa. In this case, the decision might have more to do with developer skills and which language the developer(s) is(are) more comfortable with. Michael Hodnick www.kindohm.com
Mike Hodnick wrote: VB.Net and C# are arguably becomming more and more different over time That would not surprise me. Redmond has probably heard a lot of whining from C# developers to the effect of: "When we used C++ we never had to bother with developing a good user interface, since that was basically impossible, and so we had that extra time to bash VB developers instead. Now not only are we expected to create decent GUI's, but we really can't whine about VB anymore. Why can't you make C# 'better' so we can get back to the good 'ol days?" And they are probably concerned that Sun is telling all the Java developers "C# may look like Java, but it's really just VB." :->