Is VB.Net under-rated?
-
I've been using VB since VB6 almost 20 years ago and have used it to build full blown accounting systems and many other business applications. I have never found it lacking for anything I needed to do but what bugs me is that whenever I read articles about Visual Studio, the focus is on c++ and c# and VB is relegated to footnotes or sometimes entirely forgotten. Many times I've thought of switching to one of the C based languages but is there actually a reason for me to delve into this?
C# and VB.NET can be translated to each other by a machine; it's mostly different keywords in a different order. C# is as C-based as VB.NET is VB6 based; they share stuff, but that's it. VB.NET is not "underrated", but it is assumed that anyone who does VB.NET can at least "read" C# code, as the used framework is the same.
Chris Nic wrote:
but is there actually a reason for me to delve into this?
If there's no need for it, you could do it for fun. GitHub - icsharpcode/CodeConverter: Convert code from C# to VB.NET and vice versa using Roslyn[^] Has a visual studio extension; you could have VS translate a random page of VB.NET of your current projects to see how the C# equivalent looks.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
C# and VB.NET mostly share the same language features, and, of course, they both have access to the entire .NET Framework. The problem with VB.NET is it's verbose, and it's currently not really supported by .NET Core 3.x yet. There's console app and unit test support, but nothing for WPF or WinForms, though that is in development. If I were you, I would pickup C#. It's really not that much different from VB.NET. You already know most of it. You just don't realize it. You get to replace the verbosity with curly braces and semi-colons!
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave KreskowiakDave Kreskowiak wrote:
The problem with VB.NET is it's verbose,
I actually miss that about VB.NET since I've been doing C# for so long now. I'd much rather have a bunch of "end"s instead of a bunch of "}"s all strung together.
Social Media - A platform that makes it easier for the crazies to find each other. Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
I've been using VB since VB6 almost 20 years ago and have used it to build full blown accounting systems and many other business applications. I have never found it lacking for anything I needed to do but what bugs me is that whenever I read articles about Visual Studio, the focus is on c++ and c# and VB is relegated to footnotes or sometimes entirely forgotten. Many times I've thought of switching to one of the C based languages but is there actually a reason for me to delve into this?
I used to use VB and then VB.Net but most jobs are looking for C# so I switched. The switch was very easy, but part of that was because I started out in Pascal and C to begin with. I do miss some of the easier things in VB but switching to C# was easy to do. A lot of developers seem to have a superior view of themselves and C#, likely because of the word "Basic" in VB, but as you said, I never had a business requirement not be able to be met by VB. Years ago I wrote a chat application and chat server that interfaced with an Avaya phone system and did that in VB.
Social Media - A platform that makes it easier for the crazies to find each other. Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
I used to use VB and then VB.Net but most jobs are looking for C# so I switched. The switch was very easy, but part of that was because I started out in Pascal and C to begin with. I do miss some of the easier things in VB but switching to C# was easy to do. A lot of developers seem to have a superior view of themselves and C#, likely because of the word "Basic" in VB, but as you said, I never had a business requirement not be able to be met by VB. Years ago I wrote a chat application and chat server that interfaced with an Avaya phone system and did that in VB.
Social Media - A platform that makes it easier for the crazies to find each other. Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
ZurdoDev wrote:
A lot of developers seem to have a superior view of themselves and C#, likely because of the word "Basic"
Most devs' don't seem to understand that C# is a VB, just with different keywords. It is a runtime, like VB, compiles to a p-code, and has a memory manager.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
ZurdoDev wrote:
A lot of developers seem to have a superior view of themselves and C#, likely because of the word "Basic"
Most devs' don't seem to understand that C# is a VB, just with different keywords. It is a runtime, like VB, compiles to a p-code, and has a memory manager.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
Good point. :thumbsup:
Social Media - A platform that makes it easier for the crazies to find each other. Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
I've been using VB since VB6 almost 20 years ago and have used it to build full blown accounting systems and many other business applications. I have never found it lacking for anything I needed to do but what bugs me is that whenever I read articles about Visual Studio, the focus is on c++ and c# and VB is relegated to footnotes or sometimes entirely forgotten. Many times I've thought of switching to one of the C based languages but is there actually a reason for me to delve into this?
Like you I built a lot of very valid business applications in VB6 then VB.net In the early days of the .net era I found the lack of VB.net examples and support extremely frustrating and changed to c#, the wealth of c# code out there is just incredible and was well worth the minimal pain of changing to c#. There is no better reason to change (except possibly the lack of support for VB in Code).
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
ZurdoDev wrote:
A lot of developers seem to have a superior view of themselves and C#, likely because of the word "Basic"
Most devs' don't seem to understand that C# is a VB, just with different keywords. It is a runtime, like VB, compiles to a p-code, and has a memory manager.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
I used to use VB and then VB.Net but most jobs are looking for C# so I switched. The switch was very easy, but part of that was because I started out in Pascal and C to begin with. I do miss some of the easier things in VB but switching to C# was easy to do. A lot of developers seem to have a superior view of themselves and C#, likely because of the word "Basic" in VB, but as you said, I never had a business requirement not be able to be met by VB. Years ago I wrote a chat application and chat server that interfaced with an Avaya phone system and did that in VB.
Social Media - A platform that makes it easier for the crazies to find each other. Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
ZurdoDev wrote:
A lot of developers seem to have a superior view of themselves and C#, likely because of the word "Basic" in VB
Yes, this arrogance (based upon a false premise) is something that annoys me too.
-
Like you I built a lot of very valid business applications in VB6 then VB.net In the early days of the .net era I found the lack of VB.net examples and support extremely frustrating and changed to c#, the wealth of c# code out there is just incredible and was well worth the minimal pain of changing to c#. There is no better reason to change (except possibly the lack of support for VB in Code).
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
Mycroft Holmes wrote:
I found the lack of VB.net examples and support extremely frustrating and changed to c#, the wealth of c# code out there is just incredible and was well worth the minimal pain of changing to c#. There is no better reason to change
Yup, I could see how it was going to go with VB.Net and changed to C# for the same sort of reasons.