Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. The Lounge
  3. Is VS 2022 ready for prime time?

Is VS 2022 ready for prime time?

Scheduled Pinned Locked Moved The Lounge
helpcsharpcssvisual-studioquestion
21 Posts 13 Posters 2 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B BryanFazekas

    My organization has dozens of small C# projects, compiled in every version of VS that has been published, and some have not been recompiled in a decade (not broken, don't fix it!). Unfortunately, as time marches on, the older code is less and less likely to compile successfully in newer versions of C#/VS. I'm looking at upgrading some of the programs to either VS 2019 or 2022. Moving to VS 2022 provides a longer lifespan before it's sunsetted (01/13/2032), at which point I should be retired and it will no longer be my problem. Is VS 2022 ready for usage, or does MS need to fix more things first?

    R Offline
    R Offline
    Rick York
    wrote on last edited by
    #10

    Visual Studio has been out since 1997. C# did not appear in it until 2003 2002.

    "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 DeemingR D 2 Replies Last reply
    0
    • R Rick York

      Visual Studio has been out since 1997. C# did not appear in it until 2003 2002.

      "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 DeemingR Offline
      Richard DeemingR Offline
      Richard Deeming
      wrote on last edited by
      #11

      Rick York wrote:

      C# did not appear in it until 2003.

      Technically, C# appeared in 1988, although that version was never released: :) My History of Visual Studio (Part 1) | Microsoft Docs[^]


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

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

      R K 2 Replies Last reply
      0
      • Richard DeemingR Richard Deeming

        Rick York wrote:

        C# did not appear in it until 2003.

        Technically, C# appeared in 1988, although that version was never released: :) My History of Visual Studio (Part 1) | Microsoft Docs[^]


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

        R Offline
        R Offline
        Rick York
        wrote on last edited by
        #12

        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 DeemingR 1 Reply Last reply
        0
        • R 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 DeemingR Offline
          Richard DeemingR Offline
          Richard Deeming
          wrote on last edited by
          #13

          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

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

          1 Reply Last reply
          0
          • B BryanFazekas

            My organization has dozens of small C# projects, compiled in every version of VS that has been published, and some have not been recompiled in a decade (not broken, don't fix it!). Unfortunately, as time marches on, the older code is less and less likely to compile successfully in newer versions of C#/VS. I'm looking at upgrading some of the programs to either VS 2019 or 2022. Moving to VS 2022 provides a longer lifespan before it's sunsetted (01/13/2032), at which point I should be retired and it will no longer be my problem. Is VS 2022 ready for usage, or does MS need to fix more things first?

            R Offline
            R Offline
            RedDk
            wrote on last edited by
            #14

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

            1 Reply Last reply
            0
            • Richard DeemingR Richard Deeming

              Rick York wrote:

              C# did not appear in it until 2003.

              Technically, C# appeared in 1988, although that version was never released: :) My History of Visual Studio (Part 1) | Microsoft Docs[^]


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

              K Offline
              K Offline
              kmoorevs
              wrote on last edited by
              #15

              :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"

              1 Reply Last reply
              0
              • B BryanFazekas

                My organization has dozens of small C# projects, compiled in every version of VS that has been published, and some have not been recompiled in a decade (not broken, don't fix it!). Unfortunately, as time marches on, the older code is less and less likely to compile successfully in newer versions of C#/VS. I'm looking at upgrading some of the programs to either VS 2019 or 2022. Moving to VS 2022 provides a longer lifespan before it's sunsetted (01/13/2032), at which point I should be retired and it will no longer be my problem. Is VS 2022 ready for usage, or does MS need to fix more things first?

                G Offline
                G Offline
                Gjeltema
                wrote on last edited by
                #16

                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.

                1 Reply Last reply
                0
                • R Rick York

                  Visual Studio has been out since 1997. C# did not appear in it until 2003 2002.

                  "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?"

                  D Offline
                  D Offline
                  dandy72
                  wrote on last edited by
                  #17

                  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.

                  R 1 Reply Last reply
                  0
                  • O obermd

                    VS 2017 seems to finally be stable.

                    A Offline
                    A Offline
                    AFell2
                    wrote on last edited by
                    #18

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

                    1 Reply Last reply
                    0
                    • D 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.

                      R Offline
                      R Offline
                      Rick York
                      wrote on last edited by
                      #19

                      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?"

                      1 Reply Last reply
                      0
                      • B BryanFazekas

                        My organization has dozens of small C# projects, compiled in every version of VS that has been published, and some have not been recompiled in a decade (not broken, don't fix it!). Unfortunately, as time marches on, the older code is less and less likely to compile successfully in newer versions of C#/VS. I'm looking at upgrading some of the programs to either VS 2019 or 2022. Moving to VS 2022 provides a longer lifespan before it's sunsetted (01/13/2032), at which point I should be retired and it will no longer be my problem. Is VS 2022 ready for usage, or does MS need to fix more things first?

                        S Offline
                        S Offline
                        Stepan Hakobyan
                        wrote on last edited by
                        #20

                        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.

                        B 1 Reply Last reply
                        0
                        • S 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.

                          B Offline
                          B Offline
                          BryanFazekas
                          wrote on last edited by
                          #21

                          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.

                          1 Reply Last reply
                          0
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • World
                          • Users
                          • Groups