So... Is Visual Basic officially dead?
-
I'm working for a customer who uses Visual Basic. VB was my first language so I don't mind too much, although after years of C# it feels a bit bloated and archaic at times. I still have another VB project as well, so at least I knew what to expect. It's an old web forms project though, so all in all it's pretty meh X| So anyway, I had to start a new project (not something they do often, they basically have the one monolith) and thought I'd pick a VB project template since that's what the client is using. I have VB templates for WPF, WCF, Console, Library, WinForms and Test projects But as soon as I filter on the more modern project types, like Web, Web API, Cloud, Games or Blazor, I get zero templates. Ended up picking C# instead, as those are readily available. I remember reading Microsoft isn't actively developing VB anymore and I'm pretty sure the earlier version of .NET Core did not support VB. When googling the subject I find a mix of "VB dead" and "VB coming to .NET (Core)", but evidence would suggest it never actually came to .NET (Core). All in all it seems to me like Microsoft pulled the plug or is this wishful thinking?
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
I'm working for a customer who uses Visual Basic. VB was my first language so I don't mind too much, although after years of C# it feels a bit bloated and archaic at times. I still have another VB project as well, so at least I knew what to expect. It's an old web forms project though, so all in all it's pretty meh X| So anyway, I had to start a new project (not something they do often, they basically have the one monolith) and thought I'd pick a VB project template since that's what the client is using. I have VB templates for WPF, WCF, Console, Library, WinForms and Test projects But as soon as I filter on the more modern project types, like Web, Web API, Cloud, Games or Blazor, I get zero templates. Ended up picking C# instead, as those are readily available. I remember reading Microsoft isn't actively developing VB anymore and I'm pretty sure the earlier version of .NET Core did not support VB. When googling the subject I find a mix of "VB dead" and "VB coming to .NET (Core)", but evidence would suggest it never actually came to .NET (Core). All in all it seems to me like Microsoft pulled the plug or is this wishful thinking?
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
I wouldn't mourn. It was in the eighties when I wrote:
10 PRINT "Herman is the best !!1!!1!11!";;;;;
20 GOTO 10In Word you can only store 2 bytes. That is why I use Writer.
-
I wouldn't mourn. It was in the eighties when I wrote:
10 PRINT "Herman is the best !!1!!1!11!";;;;;
20 GOTO 10In Word you can only store 2 bytes. That is why I use Writer.
Clearly, the pinnacle of every VB app ever written right there.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave Kreskowiak -
I'm working for a customer who uses Visual Basic. VB was my first language so I don't mind too much, although after years of C# it feels a bit bloated and archaic at times. I still have another VB project as well, so at least I knew what to expect. It's an old web forms project though, so all in all it's pretty meh X| So anyway, I had to start a new project (not something they do often, they basically have the one monolith) and thought I'd pick a VB project template since that's what the client is using. I have VB templates for WPF, WCF, Console, Library, WinForms and Test projects But as soon as I filter on the more modern project types, like Web, Web API, Cloud, Games or Blazor, I get zero templates. Ended up picking C# instead, as those are readily available. I remember reading Microsoft isn't actively developing VB anymore and I'm pretty sure the earlier version of .NET Core did not support VB. When googling the subject I find a mix of "VB dead" and "VB coming to .NET (Core)", but evidence would suggest it never actually came to .NET (Core). All in all it seems to me like Microsoft pulled the plug or is this wishful thinking?
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
I'm working for a customer who uses Visual Basic. VB was my first language so I don't mind too much, although after years of C# it feels a bit bloated and archaic at times. I still have another VB project as well, so at least I knew what to expect. It's an old web forms project though, so all in all it's pretty meh X| So anyway, I had to start a new project (not something they do often, they basically have the one monolith) and thought I'd pick a VB project template since that's what the client is using. I have VB templates for WPF, WCF, Console, Library, WinForms and Test projects But as soon as I filter on the more modern project types, like Web, Web API, Cloud, Games or Blazor, I get zero templates. Ended up picking C# instead, as those are readily available. I remember reading Microsoft isn't actively developing VB anymore and I'm pretty sure the earlier version of .NET Core did not support VB. When googling the subject I find a mix of "VB dead" and "VB coming to .NET (Core)", but evidence would suggest it never actually came to .NET (Core). All in all it seems to me like Microsoft pulled the plug or is this wishful thinking?
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
was it ever alive ? dat it da question.
CI/CD = Continuous Impediment/Continuous Despair
-
Well, C# allows a few things which VB doesn't.
-
Well, C# allows a few things which VB doesn't.
And VB has
On Error Resume Nextwhich is a damn good reason for killing it! :-D"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Clearly, the pinnacle of every VB app ever written right there.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave KreskowiakWhen I was in high school, some wizard wrote a Fortran program nicknamed The Black Death. It entered an infinite loop that printed solid lines of asterisks. It was soon outdone by The White Death, which entered an infinite loop that "printed" form feeds.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
I'm working for a customer who uses Visual Basic. VB was my first language so I don't mind too much, although after years of C# it feels a bit bloated and archaic at times. I still have another VB project as well, so at least I knew what to expect. It's an old web forms project though, so all in all it's pretty meh X| So anyway, I had to start a new project (not something they do often, they basically have the one monolith) and thought I'd pick a VB project template since that's what the client is using. I have VB templates for WPF, WCF, Console, Library, WinForms and Test projects But as soon as I filter on the more modern project types, like Web, Web API, Cloud, Games or Blazor, I get zero templates. Ended up picking C# instead, as those are readily available. I remember reading Microsoft isn't actively developing VB anymore and I'm pretty sure the earlier version of .NET Core did not support VB. When googling the subject I find a mix of "VB dead" and "VB coming to .NET (Core)", but evidence would suggest it never actually came to .NET (Core). All in all it seems to me like Microsoft pulled the plug or is this wishful thinking?
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
VB is among the walking dead of programming languages. Ruby is its sidekick. There's undoubtedly more.
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domain -
It's more down to the editors and compilers supporting the language. I could undoubtedly compile my own VB files and run them on .NET 6 (I'm assuming the resulting MSIL will run fine, but it isn't guaranteed as Microsoft seems to have dropped support). However, Visual Studio doesn't support VB projects anymore, so I'd have to do it all manually, which is a pain, and not viable for a professional project. And, as said, it's not VB.NET generating the MSIL, but the compiler, and when Microsoft drops support for that, it could be possible that VB.NET becomes incompatible with newer versions of the framework.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
was it ever alive ? dat it da question.
CI/CD = Continuous Impediment/Continuous Despair
Judging from the amount of VB code that's still around it was very much alive.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
I'm working for a customer who uses Visual Basic. VB was my first language so I don't mind too much, although after years of C# it feels a bit bloated and archaic at times. I still have another VB project as well, so at least I knew what to expect. It's an old web forms project though, so all in all it's pretty meh X| So anyway, I had to start a new project (not something they do often, they basically have the one monolith) and thought I'd pick a VB project template since that's what the client is using. I have VB templates for WPF, WCF, Console, Library, WinForms and Test projects But as soon as I filter on the more modern project types, like Web, Web API, Cloud, Games or Blazor, I get zero templates. Ended up picking C# instead, as those are readily available. I remember reading Microsoft isn't actively developing VB anymore and I'm pretty sure the earlier version of .NET Core did not support VB. When googling the subject I find a mix of "VB dead" and "VB coming to .NET (Core)", but evidence would suggest it never actually came to .NET (Core). All in all it seems to me like Microsoft pulled the plug or is this wishful thinking?
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Sometimes I feel like I am beating a dead Horse. :( First, Haters are going to hate. Second, programmers, for the most part, like and defend the language they know best, and disparage almost every other. Third, VB isn't "cool" anymore. Fourth, the main problem with VB is the word "Basic" in the name. Particularly the "B" which stands for "Beginners". For Sander. No, it is not dead. See steveb's post above about MSIL. For Griff I sincerely, greatly appreciate your knowledge, wisdom, and the fact you help a whole lot of people in this site, myself included. However, if you don't like "OnError Resume Next", or "OnError GoTo" (which is also found in C#), then DON'T USE THEM. Saying that VB should be dropped because of those statements, is like saying all tigers, extremely beautiful animals, should be killed because they might bite your head off when you try to pet them. Or saying that most women should be killed because they are a PITA. IMO this is not only foolish, but ridiculous. Finally, I am pretty sure that quite a lot of businesses are still using VB6 and VB.net to run their business, if not the majority. And I apologize for not being one of the "cool kids" and being subject to my second observation above myself.
Sometimes one man's trash is just trash, but not in the case of VB.
-
was it ever alive ? dat it da question.
CI/CD = Continuous Impediment/Continuous Despair
It pioneered component (vs object) oriented development; a pattern which is useful today.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
And VB has
On Error Resume Nextwhich is a damn good reason for killing it! :-D"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Sometimes I feel like I am beating a dead Horse. :( First, Haters are going to hate. Second, programmers, for the most part, like and defend the language they know best, and disparage almost every other. Third, VB isn't "cool" anymore. Fourth, the main problem with VB is the word "Basic" in the name. Particularly the "B" which stands for "Beginners". For Sander. No, it is not dead. See steveb's post above about MSIL. For Griff I sincerely, greatly appreciate your knowledge, wisdom, and the fact you help a whole lot of people in this site, myself included. However, if you don't like "OnError Resume Next", or "OnError GoTo" (which is also found in C#), then DON'T USE THEM. Saying that VB should be dropped because of those statements, is like saying all tigers, extremely beautiful animals, should be killed because they might bite your head off when you try to pet them. Or saying that most women should be killed because they are a PITA. IMO this is not only foolish, but ridiculous. Finally, I am pretty sure that quite a lot of businesses are still using VB6 and VB.net to run their business, if not the majority. And I apologize for not being one of the "cool kids" and being subject to my second observation above myself.
Sometimes one man's trash is just trash, but not in the case of VB.
I think Sanders point was that the tooling for VB.Net is lagging behind the more main stream c#. And yeah lots of people like to kick the old VB dog but there are also a lot of us that cut our teeth on it. I got a hell of a shock a few years ago when I tried to show a newbie (school kid) how vb worked, I could it even connect to the database it had changed so much.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
I'm working for a customer who uses Visual Basic. VB was my first language so I don't mind too much, although after years of C# it feels a bit bloated and archaic at times. I still have another VB project as well, so at least I knew what to expect. It's an old web forms project though, so all in all it's pretty meh X| So anyway, I had to start a new project (not something they do often, they basically have the one monolith) and thought I'd pick a VB project template since that's what the client is using. I have VB templates for WPF, WCF, Console, Library, WinForms and Test projects But as soon as I filter on the more modern project types, like Web, Web API, Cloud, Games or Blazor, I get zero templates. Ended up picking C# instead, as those are readily available. I remember reading Microsoft isn't actively developing VB anymore and I'm pretty sure the earlier version of .NET Core did not support VB. When googling the subject I find a mix of "VB dead" and "VB coming to .NET (Core)", but evidence would suggest it never actually came to .NET (Core). All in all it seems to me like Microsoft pulled the plug or is this wishful thinking?
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
This might be an interesting read, describes some VB follow up tools. - RAD Basic releases third alpha • The Register[^]
-
This might be an interesting read, describes some VB follow up tools. - RAD Basic releases third alpha • The Register[^]
And RemObjects "Mercury": VB for all platforms ... for a bunch of $$$ but it exists!
I cannot remember: What did I before google?
-
I'm working for a customer who uses Visual Basic. VB was my first language so I don't mind too much, although after years of C# it feels a bit bloated and archaic at times. I still have another VB project as well, so at least I knew what to expect. It's an old web forms project though, so all in all it's pretty meh X| So anyway, I had to start a new project (not something they do often, they basically have the one monolith) and thought I'd pick a VB project template since that's what the client is using. I have VB templates for WPF, WCF, Console, Library, WinForms and Test projects But as soon as I filter on the more modern project types, like Web, Web API, Cloud, Games or Blazor, I get zero templates. Ended up picking C# instead, as those are readily available. I remember reading Microsoft isn't actively developing VB anymore and I'm pretty sure the earlier version of .NET Core did not support VB. When googling the subject I find a mix of "VB dead" and "VB coming to .NET (Core)", but evidence would suggest it never actually came to .NET (Core). All in all it seems to me like Microsoft pulled the plug or is this wishful thinking?
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Darwin's Theory: Humans are a product of development and what is produced by them falls under these rules, that means programming languages too.
-
I'm working for a customer who uses Visual Basic. VB was my first language so I don't mind too much, although after years of C# it feels a bit bloated and archaic at times. I still have another VB project as well, so at least I knew what to expect. It's an old web forms project though, so all in all it's pretty meh X| So anyway, I had to start a new project (not something they do often, they basically have the one monolith) and thought I'd pick a VB project template since that's what the client is using. I have VB templates for WPF, WCF, Console, Library, WinForms and Test projects But as soon as I filter on the more modern project types, like Web, Web API, Cloud, Games or Blazor, I get zero templates. Ended up picking C# instead, as those are readily available. I remember reading Microsoft isn't actively developing VB anymore and I'm pretty sure the earlier version of .NET Core did not support VB. When googling the subject I find a mix of "VB dead" and "VB coming to .NET (Core)", but evidence would suggest it never actually came to .NET (Core). All in all it seems to me like Microsoft pulled the plug or is this wishful thinking?
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Darwin's Theory: Humans are a product of evolution and what is produced by them falls under these rules, that means programming languages too.
-
Sometimes I feel like I am beating a dead Horse. :( First, Haters are going to hate. Second, programmers, for the most part, like and defend the language they know best, and disparage almost every other. Third, VB isn't "cool" anymore. Fourth, the main problem with VB is the word "Basic" in the name. Particularly the "B" which stands for "Beginners". For Sander. No, it is not dead. See steveb's post above about MSIL. For Griff I sincerely, greatly appreciate your knowledge, wisdom, and the fact you help a whole lot of people in this site, myself included. However, if you don't like "OnError Resume Next", or "OnError GoTo" (which is also found in C#), then DON'T USE THEM. Saying that VB should be dropped because of those statements, is like saying all tigers, extremely beautiful animals, should be killed because they might bite your head off when you try to pet them. Or saying that most women should be killed because they are a PITA. IMO this is not only foolish, but ridiculous. Finally, I am pretty sure that quite a lot of businesses are still using VB6 and VB.net to run their business, if not the majority. And I apologize for not being one of the "cool kids" and being subject to my second observation above myself.
Sometimes one man's trash is just trash, but not in the case of VB.
Yeah, I agree with you on all points.
Slow Eddie wrote:
For Sander. No, it is not dead. See steveb's post above about MSIL.
See my reply though. The tooling seems to lag behind and Microsoft seems to not update VB anymore, making the gap with C# even bigger in the future. Sure it's not "dead" because many people and companies still use it, but it doesn't seem like a good alternative for new development anymore. In the end, VB.NET can do everything C# can (or it could a few years ago) and you can write good and bad code in both languages, but how long will this be true? So by "dead" I mean Microsoft isn't actively developing it anymore, making it a no-go for new development.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
