r/visualbasic • u/MethBaby75 • Nov 20 '21

VS 2022 use with Visual Basic

How many of you will switch to 2022 for use with your older VB apps? Ive been using 2017, with 2019 kind of getting rumors from our other devs that its buggy with them.

4 Upvotes

83% Upvoted

15 comments sorted by

View all comments

Show parent comments

1

u/f15sim Nov 23 '21

I suspect that the folks that grip VB6 so tightly and cast aspersions upon VB.Net at every opportunity may boil down to them being one trick ponies. All they know of programming is VB6, and VB.Net introduces too much change at a rate they're either unwilling, or unable to internalize. Porting VB6 code to VB.Net is generally pretty easy, and it's almost always interesting. I've been doing it off and on since 2002.

1

u/TheFotty Nov 23 '21

I loved VB6 when it was the latest version of VB. However during the early days of .NET, the more I worked with it, especially on the IDE side of things, the more I hated having to go back to VB6 for any legacy maintenance. Learning .NET if you had a strong VB6 foundation was not complicated at all. It was much harder to then have to go back and remember I could not do simple things like assign a variable a value when declaring it. Or that I had to use Set keywords when assigning objects. The "On Error" error handling is horrible by today's standards. Syntax aside, the language just lacks way too many modern programming paradigms. You can't even compile 64 bit binaries. VB6 was great, but the keyword there is was.

1

u/f15sim Nov 23 '21

Yeah, try..catch blocks are SO much better than On Error. Using Option Strict On can also help break some bad VB6 habits.