Is VS 2022 ready for prime time?

Rick York

It was designed in 2000 and first released in 2003 : C Sharp (programming language) - Wikipedia[^]

"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"

Richard Deeming

My History of Visual Studio (Part 1) | Microsoft Docs[^]:

So where am I? Ah yes, 1988. The project I’d been hired to work on was cancelled after a few months (I expect I’m in good company on that score), that project by the way was a cute variant on the C language designed for incremental compilation – it was called, cough, C#. Strangely, through the lens of 2009, it looks remarkably like what you would get if you tried to make C.Net.

"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

RedDk

:thumbsdown:VS 2022 (page does not exist):thumbsup: :squishing noise:

kmoorevs

:thumbsup: That was an excellent read! :) Thank You! (kept me from actually working for > 15 minutes at least!)

"Go forth into the source" - Neal Morse "Hope is contagious"

Gjeltema

We migrated to it a week after release (always wait for at least the X.0.1 release!). We've not had any issues at all with it - it's been remarkably smooth. It'll take up more memory because they (finally) converted it to 64 bit, but there's a number of gains that were realized because of that conversion. We have a variety of applications as well, and solutions with over a hundred projects of varying types, though we've done pretty good at getting everything to be "standardized" on targeting either .Net 4.8 or .Net 6 (we did quick upgrades after release for all our .Net core based applications). I personally like it quite a bit. They cleaned up the dark mode as well so there's no longer random bright glaring controls or panels running around.

dandy72

Rick York wrote:

C# did not appear in it until 2003.

My archives folder shows VS6 VS97 VS2002 (.NET 1.0) VS2003 (.NET 1.1) VS2005 (.NET 2.0) . . . When mounting the ISO for VS 2002, I can see most of files have a timestamp of January 2002. This is where .NET was introduced. C# was very much part of it.

AFell2

...only because MS Devs are not really messing with it anymore.

Rick York

Yes, 2002 is the correct year. I had all of those versions of VS except for 2002. I never used that one. I remember joining the MSDN and getting NT when it was in beta and installing VS97 on it. The next several years were very enjoyable.

"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"

Stepan Hakobyan

VS2022 have more problems with TFS and SCE then before, and of course older problems are not solved. I have problems building and COM registering dlls. Using VS2019 for that. I have problems with nesting files in Solution Explorer, it was solved in VS2019, and got broken in VS2022. Got some problems with ATL C++ project but that was fixed in an update. As you can see I'm not happy. Still, my org is trying to move some services to .NET 6 witch is not possible in VS2019.

BryanFazekas

Thanks for the feedback. In general it appears VS 2022 is fine, but from your feedback and others I've followed, there are a lot of irritating details. Everything I'm working on is either in framework 4.8 or being migrated to 4.8, so I'm not seeing a pressing need to upgrade to 2022. I am going to recommend to management that we look at .NET 6 for all future projects.