I first learned how to program in VB4. I can see why as a professional programmer it lost favor, but it was a great learning language.
Microsoft plots the end of Visual Basic
11–20 of 292 posts
Re: Microsoft plots the end of Visual Basic
#12I loved VB6. Of all the languages and IDE's I've ever used, I've never been more efficient in any other one. As long as MS doesn't break my workarounds to run that old IDE or its EXE's, I'm happy. VB.NET was a great stepping stone, but after switching to C# I never looked back. The only thing I miss is global functions that don't need a class qualifier in front of them. And I still find the Edit-and-Continue debuggin…
I used to think this too, but everything you can do in VB6 you can do in powershell, and do it better. Try/Catch, windows forms.. literally anything you can think of.
You can even mix powershell and C# together in the same script.
Once I realized I had a better version of everything I wanted, it became my new favorite.
Re: Microsoft plots the end of Visual Basic
#13I evaluated Visual Basic as an alternative to Borland C++ to develop Windows programs. It was just not there. Borland C++ allowed easy GUI design and was easy integrated with Windows APIs for any low-level needs.
Several years later the jump in quality was astonishing. Good ODBC drivers and easy linking between database rows and your UI make it a fast development tool that fit many needs.
I do not miss the big colored buttons that many developers used at the time. Never as bad as Access applications used to be, thou.
Re: Microsoft plots the end of Visual Basic
#14The adblocker doorslammed me. Here's the text of the article. Microsoft said this week that it will support Visual Basic on .NET 5.0 but will no longer add new features or evolve the language. “Starting with .NET 5, Visual Basic will support Class Library, Console, Windows Forms, WPF, Worker Service, [and] ASP.NET Core Web API … to provide a good path forward for the existing VB customer who want [sic] to migrate the…
At the bottom you can click “move on to site.”
Re: Microsoft plots the end of Visual Basic
#15The end of Visual Basic.NET, that is. "Classic" Visual Basic has been ended for a long time now. (And VB.NET is much less of a loss -- it was never as popular as classic VB. Even when it first came out, it was clear that if you were a VB developer, Microsoft really wanted you to move to C#; VB.NET always felt like an afterthought, a fig leaf they could use to say they really weren't abandoning VB when they obviously…
> "Classic" Visual Basic has been ended for a long time now.
It kinda still lives on in classic ASP. It will be supported indefinitely so far [1]
[1] https://support.microsoft.com/en-us/help/2669020/active-serv...
Re: Microsoft plots the end of Visual Basic
#16Wonder what is going to happen to Visual Basic for Applications? I hope it pushes Microsoft to move toward a new language like Python to automate Excel.
Re: Microsoft plots the end of Visual Basic
#17I loved VB6. Of all the languages and IDE's I've ever used, I've never been more efficient in any other one. As long as MS doesn't break my workarounds to run that old IDE or its EXE's, I'm happy. VB.NET was a great stepping stone, but after switching to C# I never looked back. The only thing I miss is global functions that don't need a class qualifier in front of them. And I still find the Edit-and-Continue debuggin…
`using static` goes some way toward simulating free functions in C#.
Re: Microsoft plots the end of Visual Basic
#18The end of Visual Basic.NET, that is. "Classic" Visual Basic has been ended for a long time now. (And VB.NET is much less of a loss -- it was never as popular as classic VB. Even when it first came out, it was clear that if you were a VB developer, Microsoft really wanted you to move to C#; VB.NET always felt like an afterthought, a fig leaf they could use to say they really weren't abandoning VB when they obviously…
[deleted]
Re: Microsoft plots the end of Visual Basic
#19I loved VB6. Of all the languages and IDE's I've ever used, I've never been more efficient in any other one. As long as MS doesn't break my workarounds to run that old IDE or its EXE's, I'm happy. VB.NET was a great stepping stone, but after switching to C# I never looked back. The only thing I miss is global functions that don't need a class qualifier in front of them. And I still find the Edit-and-Continue debuggin…
About global functions, you can do the same with “using static”, see https://docs.microsoft.com/en-us/dotnet/csharp/language-refe...
Re: Microsoft plots the end of Visual Basic
#20I had 7 years of C# experience in 2015 when I had to make an unanticipated job change. With some trepidation, I took a position with another company in the same industry whose codebase was all vb.net. I used Telerik's code converter a lot to bootstrap my proficiency with vb syntax. The boss said I could just write in C# if I wanted to, but I saw no need to make more mental work for the rest of the team.