Printable View
I've been using Visual Basic 2010 with Windows 7 for ages, but I want to try the newer versions VB in virtual machines. Which version of Visual Basic works best (little performance and other annoyance issues) with your version of Windows?
Experiencing how dead the General PC forum is, is why I posted my question here.
Would really like to know what you're working with, so I can play with these versions myself. :)
At home W7 and vsxxxx to 2010, also a laptop with W10 for remote work (unfortunately my XP PC broke down lately so I'm just using a virtual XP).
At work one to be dismissed with W7 and vsxxxx to 2015 and a newer with W11, a broke vs2015 version and vs2019 .
I have long stated that VS2010 was the most beautiful release of VS. I'm not so sure about that anymore. Both VS2019 and VS2022 were also quite nice. You pretty much must have an SSD for those to be all that smooth, but if you have an SSD, then the performance is quite good.
The issue with these recent versions of VS is the amount of graphical feedback they have. You can get snapshots, peeks, previews, and whatever else they call different looks at code you aren't currently working on. You also have at least three rails in the vertical slider on the code page, with different indicators (like errors, breakpoints, bookmarks, etc.) showing up in different rails. This can result in a very colorful vertical slider, as there are red segments, red dots, maroon dots, blue dots, yellow dots, all in different parts of the slider. The problem is that all of these graphical feedback features come at computational cost, and I doubt that a single person uses more than a fraction of all of them. I'd like to see more opt-out on these features, such that you could reduce the computational overhead of the features that you don't make use of. However, I'd want it to be opt-out, because when you DO want a feature, they're really quite nice, and if they were opt-in, then you'd likely never even know about most of them. Heck, the Options menu is currently so extensive that it seems unlikely anybody fully knows or understands all the things you can turn on and off already, and here I am asking for more.
Ultimately, I feel that VS2019 and VS2022 (and therefore, why bother with VS2019?) are more visually pleasing than VS2010 was, and have more features as well. I still have VS2010 on some computers, but have moved all new development over to VS2022, except for the one system that lacks enough space for both VS2022 and VS2019....and the explanation for what I have on there can best be summarized as inertia.
I'm using Win10 on some computers and Win11 on one of the Surface Pros, largely because it was automatically pushed there. I might be able to put Win11 on one of the others, or else it lacks some hardware. I haven't gone looking at that. I built that computer, and it came with a small chip that I could plug in, which might be whatever that on-board security feature that Win11 requires. I didn't plug it in, at the time, and now I'd have to dig out the manual to figure out what that chip is, to see if it would allow me to go to Win11 on that computer...and I haven't gotten around to it, because it doesn't seem all that important.
You don't need a chip to run w11, MS had so much bashing that they made a registry setting 0,1 to get past it.
Yeah, but I HAVE a chip. I don't remember what the chip is for, and I never plugged it in, but I do HAVE it.
I don't see much of a difference between W10 and W11. If it gets pushed to me automatically, then I'm fine with that. If it doesn't, then I'm also fine with that. The Surface Pro 7 got W11 automatically. The Surface Pro 2 lacked the requirements, and has not gotten W11. My desktop is on W10, and that's the one that I could add that chip to...whatever that chip is, and whatever it does. It was something about some kind of security, so I'm thinking it might be what W11 wanted. Might look it up some day.
When a guy with a chip on his shoulder said, toss off buddy she is mine.
I installed an SSD a year ago, with a terabyte of space, but I'm not sure if my PC can handle VS 2019 and 2022 if it's so graphical. It's CPU is an i7-2600, with a weak Nvidia card that has about 144 Cuda cores. I've upped the system to 16GB of ram two years ago, so I'll experiment with the versions you guys mentioned. I know Windows 10 works great in a virtual machine.
The graphics it uses is not so much of a challenge. I have it on a Surface Pro 2 and Surface Pro 7, neither of which has a powerful graphics card. It runs just fine on those. The issue is that there is a LOT of code that has to be loaded for all parts to work well. That makes loading times slow on a spinning platter. With an SSD, the load times are about as fast as VS2010.
From your specs I don't see an issue with 2019 , haven't used 2022.
Win7 and VS2022 for C++. VS2022 install says it isn't supported for W7 - but it does install and work OK (for c/c++) and a reported W7 problem in an earlier 2022 release was fixed in the next. The current version (17.4.3) AFAIK is stable with W7 for c/c++.
I installed Visual Studio 2019 on Windows 10 in a virtual machine. The only issue I have, which is not VS related, is that the latest Windows 10, 22H2, takes forever to boot-up from my SSD. I managed to speed it up some by disabling alot of unneeded services, but the boot-up is still about 4 times slower than Windows 7.Quote:
Originally Posted by Shaggy Hiker
Quote:
Originally Posted by sapator
I installed Visual Studio 2022 on Windows 7 yesterday, and it only had one issue at the end, but it worked when I launched it. I don't remember the error code, but it informed me to view the installation log to see what it couldn't install, which I did, but the log showed no issues. Anyway, I uninstalled it and installed Visual Studio 2019 on Windows 10 with no issues. I was gonna install VS 2022 on 10, but after reading about Win 10's slow boot-up time (which I'm experiencing), I figured VS 2022 might make it even more slower.Quote:
Originally Posted by 2kaud
I've never had an issue with boot time on either Win10 or Win11, for what little that is worth.
Everything is fine now. I discovered last night that I mistakenly created my Windows 10 virtual machine on my hard drive instead of my SSD. :pQuote:
Originally Posted by Shaggy Hiker
I moved it and it's speedy.