All y'all are crazy, their downloads page has an 'older downloads' link: https://visualstudio.microsoft.com/vs/older-downloads/ edit - I'm the crazy one, because these links are defective. Microsoft has left us with a link trail eventually leading to doom. People have reported it, and Microsoft just covered their ears and spouted out some direct paths. Maybe someone from Product was standing behind them. What is this VisualStudio 2019 you speak of? I only know of our flagship VisualStudio 2026, now with Omega Copilot integration. More on reddit.com

Visual Studio 2022 will be a 64-bit application Wow. Way back they were dead set against making it 64bit. I wonder what changed? More on reddit.com

As I was very critical about the preview versions, I must say VS 2022 is solid. I migrated 9 big projects to .NET 6.0 last 2 days and I'm really very satisfied with this version. At last - VS works WITH me, not against me. However, something is wrong with... IDK, ticket system in feedback site. The bugs I reported - it seemed like they all went to /dev/null, however - in release version most of them are fixed. The tickets still hang there, don't they know they are already fixed? ;) OK, I'm most delighted with the speed, code analysis and .NET 6.0 stability. Not a single problem. It just works and it works blazing fast. It found some obsolete APIs in my code, flagged it and suggested what should it be replaced with. Piece of cake. Do not upgrade if you have a plenty of technological debt to pay. It WILL hurt, or... well, you will have some work to do to upgrade up to the modern times. It works. It works. It's fast. C#10 features now REALLY work. Nothing's broken. Issues are always precisely located, correct items are highlighted. Refactoring is fast and accurate. I refactored a huge amount of code last 2 days. Moving files and projects between directories, changed APIs, dependencies. All the time VS worked as it should, just doing its job with only a few crashes. I mean technically - it's only one issue - when you change TargetFramework in main dependency, and the rest of the projects don't support it - VS crashes, but after restarting everything works. The workaround is to start upgrading from the tree leaves, not the root (main dependency). Not a single issue with Git. For such overkill I made recently - nothing required to be fixed manually from the console. Everything was manageable from VS Git tools. BTW, the new APIs VS suggested as replacement for the deprecated ones are just better. Resulting code is smaller, faster and more readable. I tested it on Windows apps, Linux apps, services, and web apps. Even on ARM 64. No problems in building, no problems with installing and running .NET 6 on target systems. There are plenty of extensions already compatible with this version. The most important for me is Visual Studio Installer Projects, I use it a lot with Windows. It's in a preview version, but I haven't got a single issue with it. OK, the project property editor is still a little clunky and there are some things that can be set only by editing the project files manually. The XML generated by the tool is pretty ugly, so I fix it myself anyway. Also - VS property editor doesn't really get the idea of embedding files like licenses, readmes and icons. It does it wrong half of the times, so I just fix it manually later. But it's a small issue when you already know how the file should look to work properly. If you don't, here's a simple example: Readme.md Just copy and paste for all your embedded files. You specify the path only in ItemGroup, in PropertyGroup goes only the filename. Pack and PackagePath must be just as in example, can't be omitted or set any other way. Well, the PackagePath="/" also works. Also - I was an early adopter. I struggled with millions of issues on preview versions. When the stable version was finally released I already knew my way around the new project system, various quirks and features. I was pretty scared before switching to .NET 6.0 because the preview versions didn't work well for me. I was very pleasantly surprised that the stable (LTS) version doesn't really have any noticeable rough edges. BTW, the upgrade is not an option. Times are changing, tech is changing, software releasing patterns are changing. However - migrating from .NET Core 3.1 or .NET Framework to .NET 5 was difficult and tricky. Migrating from .NET 5 to .NET 6 is very easy. The new project format is much, much better because it's much simpler. The best thing about it is being multiple platform compatible. Most of the code I make works both on Linux and Windows. The desktop projects are not so very different from server backends. It's much more consistent than it was in older frameworks. It's heading in a good direction. More on reddit.com

https://aka.ms/vs/17/release/vs_community.exe More on reddit.com