|
I used it a few times. I used VB6 a lot more, my company bought a product written in classic ASP and VB6 and I had to convert it. In 2011, a guy was using VB6 because he refused to learn new things.
My work is nearly all web now, the odd mobile app
|
|
|
|
|
I had to work on a VB.NET WinForm program I wrote almost 15 years ago. Someone found an edge case bug in the program that I had to fix. I find that switching languages is not difficult for me. I mostly use C#.NET now, but I used VB.NET (and VB3 and VB4) for many years. Anyway, I fixed the bug and brought the program up to .NET 4.8. It was kind of fun actually. Beats when I had to work in Assembler and Fortran 77. 
|
|
|
|
|
It's still alive?
I don't think before I open my mouth, I like to be as surprised a everyone else.
PartsBin an Electronics Part Organizer - Release Version 1.3.0 JaxCoder.com
Latest Article: SimpleWizardUpdate
|
|
|
|
|
Yeah apparently. I saw someone else post about it, this is a reaction post
|
|
|
|
|
I worked on a legacy app about 10 years ago written in VB and had to relearn the language just enough to do the work required and hated every second of it.
Only other time was about 40 yrs. ago worked on a motor tester using HP basic and some of their hardware. It wasn't so bad as I remember but that was all I cared to do even back then. Was using assembler at the time and taught myself C and then C++ as soon as it became available.
I don't think before I open my mouth, I like to be as surprised a everyone else.
PartsBin an Electronics Part Organizer - Release Version 1.3.0 JaxCoder.com
Latest Article: SimpleWizardUpdate
|
|
|
|
|
Most of my VB work was VB6, for the same reasons, to update a legacy app
|
|
|
|
|
Yeah... it needs more than a #2 double tap[^]  
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
modified 3-Nov-23 3:53am.
|
|
|
|
|
Not dead, but "done".
We will ensure Visual Basic remains a straightforward and approachable language with a stable design. The core libraries of .NET (such as the BCL) will support VB and many of the improvements to the .NET Runtime and libraries will automatically benefit VB. When C# or the .NET Runtime introduce new features that would require language support, VB will generally adopt a consumption-only approach and avoid new syntax. We do not plan to extend Visual Basic to new workloads. We will continue to invest in the experience in Visual Studio and interop with C#, especially in core VB scenarios such as Windows Forms and libraries.
TTFN - Kent
|
|
|
|
|
|
Christian Graus wrote: Left to die on the vine
Do not worry or be sad... Seeing how much VB6 still is alive and kicking (often in the balls). I suppose you will have VB.Net until you retire.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
IMHO, VB is the easiest-to-learn visual programming environment. If only I had known about it before learning about the Message Map macros in MFC, I would have learnt things faster.
|
|
|
|
|
Amarnath S wrote: I would have learnt things faster.
Probably, but, would you have learned the correct ones?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Amarnath S wrote: the Message Map macros in MFC
I wasted far too much of my life grappling with those abominations. 
|
|
|
|
|
Caroline says she wants a language but it's just a toy.
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
In .NET it makes no sense, there is only the CLR and C# is the sensible choice - many languages have C-like syntax, only VB has VB-like syntax.
If they will ever make a native VB7 personally I will be if not the first adopter, the second. It's happening more and more that I need to put up a small interface for testing or an intelligent script with some graphic and swear against the useless complications imposed by the alternatives. I miss VB (but not On Error Resiume Next).
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
The shortest horror story: On Error Resume Next
|
|
|
|
|
den2k88 wrote: In .NET it makes no sense, there is only the CLR and C# is the sensible choice
There is only one language in .NET - MSIL. Whether C#, F#, VB, or any of a number of other "syntactic sugar" .NET languages made by MS or third parties, the language processor is responsible for converting the language code to MSIL. If MS decides not to update the VB engine to convert to newer MSIL constructs, that is their choice. I use C# 99.99% of the time, so I have not used VB in a long time (outside occasional maintenance or conversion to C#). If there is not enough of a market to support extending VB when they extend C#, then it makes sense to start sunsetting it. Personally, I prefer the VB syntax over the archaic and unnecessary curly bracket and semicolon throwbacks to the last century, but they are second nature after 20 years.
Besides, you can reference .NET libraries (whatever language they are written in) in VB (since they are compiled to MSIL), so the capabilities, if not the exact syntax, are available in VB if you want it.
|
|
|
|
|
I'm on the verge of retiring and haven't built a new commercial system for ages; when I last did, I used C#, and a couple of hobby websites I'm using C#. But I'm also still supporting VB.Net stuff (including one large commercial system) and have even found a couple of 3rd parties who are happy to take over long-term support for it.
If I need to knock up a proof-of-concept or a quick web utility for myself, I still find VB quicker than C#. And in work, I've yet to find anything I can't do in VB.Net that I can (and want to) do in C#.
But I'm a bit of a Luddite anyway.
|
|
|
|
|
|
Not enough "samples". If you have to start somewhere (with MS), finding "working samples" (C#) is a big plus.
"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
|
|
|
|
|
I treated Basic with contempt in early days. Baffled by why people used VB6 when Delphi was so much more regular and productive. However, when I first saw VB, I was impressed - at last BASIC as a real programming language, However, there was also the wonderful C# that, to me, "looked like Java and smelled like Delphi".
|
|
|
|
|
Visual Basic is not dead.
It just smells funny.
Like Jazz.
However I do think that it is doomed in the end.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
|
|
|
|
|
imo VB6 died. And VBA , VB.NET are dying.
And I am sad about it. The programming languages I have used most are VB6 and VBA. Even now, I use mainly VB6 and some VB.NET. I have NOT touched python and even C#
Now, its for VB6 and VBA users to resurrect VB6 and keep VBA alive. Microsoft abandoned VB6 and will soon abandon VB.NET and even VBA. So those who like VB6, VBA etc will have to work to keep it alive
|
|
|
|
|
Started quite a few new project using vb.net. It is a cool, chilled language, more modern than the workhorse, Delphi 7.
Used C# a lot before. As others pointed out, it is a C (as in cancer) type language driven into total chaos by the Cool Kids On The Codeblock. Release by release harder to follow the syntax incorporating things from All The Cool Languages. Including from Dartmouth BASIC 
|
|
|
|
|
Been using one flavor or
another of Basic for most of my 30+ year career including VB6 and VB.Net but I’ve not touched it since 2021. I didn’t think I would like C# at first but now I can’t really imagine ever going back to VB. But I don’t think VB will ever completely die.
|
|
|
|
|
First, What is Visual Basic?
We have VB (classic), VB-Script and VB (.Net)
The first one (VB Classic)is dead - the last version was released in 1999.
But it's coming back to live; google on TwinBasic and RadBasic.
The second one is dying (VB-Script) - Microsoft is phasing out this version of VB.
And I think that should have been done years ago, as it is only something to be used by Ransomware parties.
The third one (VB.Net).
Officially? It's alive.
Really? It's dead as the language is not evolving anymore.
But, just like for VB Classic, VB.Net is reviving.
There is a second implementation (Mercury), OpenSilver is 100% supporting VB.Net, enabling VB to do Xaml, WebAssembly and mobile, and former head of VB, Anthony D. Green has started to take up the task of supporting the VB language, adding language structs and features.
So, the answer is Yes and No.
Depending on what you think VB is and if Microsoft support defines dead.
As I see the projects outside Microsoft, VB classic and .Net both have a bright future.
But if you want to depend on MS only, they are both dead.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
