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
  1. Home
  2. The Lounge
  3. VS 2022

VS 2022

Scheduled Pinned Locked Moved The Lounge
helpcsharpvisual-studiowpfquestion
21 Posts 10 Posters 0 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.
  • Kornfeld Eliyahu PeterK Offline
    Kornfeld Eliyahu PeterK Offline
    Kornfeld Eliyahu Peter
    wrote on last edited by
    #1

    So in most part it works well (nothing astonishing in compare to 2019), however I have comfort issue... I have fixed solutions for every project I'm working on. I have shortcuts that open one solution instead of opening VS than pick the solution... I used to it and find it easy to manage and use it since the stone-ages... However 2022 crashes (at System.Windows.Media.Composition.DUCE+Channel.SyncFlush() which may hint something about WPF) using that technique... I can double-click the solution file and it will open... I can open VS and pick the solution - it works... However opening the shortcut crashes... Can anybody check this to see if it is an problem on my computer or happens to everyone (in which case I may waste my time to report a bug that will be close in a month)?

    "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

    "It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox

    OriginalGriffO S L R StarNamer workS 6 Replies Last reply
    0
    • Kornfeld Eliyahu PeterK Kornfeld Eliyahu Peter

      So in most part it works well (nothing astonishing in compare to 2019), however I have comfort issue... I have fixed solutions for every project I'm working on. I have shortcuts that open one solution instead of opening VS than pick the solution... I used to it and find it easy to manage and use it since the stone-ages... However 2022 crashes (at System.Windows.Media.Composition.DUCE+Channel.SyncFlush() which may hint something about WPF) using that technique... I can double-click the solution file and it will open... I can open VS and pick the solution - it works... However opening the shortcut crashes... Can anybody check this to see if it is an problem on my computer or happens to everyone (in which case I may waste my time to report a bug that will be close in a month)?

      "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

      OriginalGriffO Offline
      OriginalGriffO Offline
      OriginalGriff
      wrote on last edited by
      #2

      Ah. I won't be installing that in a hurry then ... I use a right-click on the taskbar to select my project from the "current crop" of pinned projects and it would be a PITA to lose that. It works in Word, Excel, and just about everything else, so why should VS suddenly lose it? Please tell me when that's fixed ... :-D

      "I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!

      "I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
      "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt

      Kornfeld Eliyahu PeterK L P 3 Replies Last reply
      0
      • Kornfeld Eliyahu PeterK Kornfeld Eliyahu Peter

        So in most part it works well (nothing astonishing in compare to 2019), however I have comfort issue... I have fixed solutions for every project I'm working on. I have shortcuts that open one solution instead of opening VS than pick the solution... I used to it and find it easy to manage and use it since the stone-ages... However 2022 crashes (at System.Windows.Media.Composition.DUCE+Channel.SyncFlush() which may hint something about WPF) using that technique... I can double-click the solution file and it will open... I can open VS and pick the solution - it works... However opening the shortcut crashes... Can anybody check this to see if it is an problem on my computer or happens to everyone (in which case I may waste my time to report a bug that will be close in a month)?

        "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

        S Offline
        S Offline
        Super Lloyd
        wrote on last edited by
        #3

        I dunno, I open pinned recent solutions on the taskbar button, and it open my project straight away fine. I am not sure if it's the same thing as your special shortcuts, but that's what I do!.... Furthermore, at work our solution has, ahem, 600 projects, I just can't work with VS2019, but VS2022 works a treat! :)

        A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!

        Kornfeld Eliyahu PeterK 1 Reply Last reply
        0
        • OriginalGriffO OriginalGriff

          Ah. I won't be installing that in a hurry then ... I use a right-click on the taskbar to select my project from the "current crop" of pinned projects and it would be a PITA to lose that. It works in Word, Excel, and just about everything else, so why should VS suddenly lose it? Please tell me when that's fixed ... :-D

          "I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!

          Kornfeld Eliyahu PeterK Offline
          Kornfeld Eliyahu PeterK Offline
          Kornfeld Eliyahu Peter
          wrote on last edited by
          #4

          It is possible (but not likely) that it is something on my side... I have 8 versions of VS installed side-by-side (too lazy to clean)... However it is the first version of VS does not play nice...

          "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

          "It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox

          J 1 Reply Last reply
          0
          • Kornfeld Eliyahu PeterK Kornfeld Eliyahu Peter

            So in most part it works well (nothing astonishing in compare to 2019), however I have comfort issue... I have fixed solutions for every project I'm working on. I have shortcuts that open one solution instead of opening VS than pick the solution... I used to it and find it easy to manage and use it since the stone-ages... However 2022 crashes (at System.Windows.Media.Composition.DUCE+Channel.SyncFlush() which may hint something about WPF) using that technique... I can double-click the solution file and it will open... I can open VS and pick the solution - it works... However opening the shortcut crashes... Can anybody check this to see if it is an problem on my computer or happens to everyone (in which case I may waste my time to report a bug that will be close in a month)?

            "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

            L Offline
            L Offline
            lmoelleb
            wrote on last edited by
            #5

            Unable to reproduce Environment: Visual Studio 2022 version 17.0.3, Windows 11 21H2 Steps to reproduce: 1) Drag an existing solution to the desktop using the right mouse button. 2) Select "Create shortcut here" in the popup menu 3) Double click the created shortcut Expected behavior: Visual Studio opens and load the solution without errors Observed behavior: Visual Studio opens and load the solution without errors

            Kornfeld Eliyahu PeterK 1 Reply Last reply
            0
            • S Super Lloyd

              I dunno, I open pinned recent solutions on the taskbar button, and it open my project straight away fine. I am not sure if it's the same thing as your special shortcuts, but that's what I do!.... Furthermore, at work our solution has, ahem, 600 projects, I just can't work with VS2019, but VS2022 works a treat! :)

              A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!

              Kornfeld Eliyahu PeterK Offline
              Kornfeld Eliyahu PeterK Offline
              Kornfeld Eliyahu Peter
              wrote on last edited by
              #6

              I do not know how pinned solution different from a classic shortcut... I have a mac-like toolbar that pops up when I hit the top side of the screen with the mouse. It holds classic shortcuts... Up until VS2019 had no problem with it...

              "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

              "It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox

              K 1 Reply Last reply
              0
              • OriginalGriffO OriginalGriff

                Ah. I won't be installing that in a hurry then ... I use a right-click on the taskbar to select my project from the "current crop" of pinned projects and it would be a PITA to lose that. It works in Word, Excel, and just about everything else, so why should VS suddenly lose it? Please tell me when that's fixed ... :-D

                "I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!

                L Offline
                L Offline
                lmoelleb
                wrote on last edited by
                #7

                Unable to reproduce Environment: Visual Studio 2022 version 17.0.3, Windows 11 21H2 Steps to reproduce: 1) Make sure at least one solution has been opened in VS2022. 2) Make sure VS2022 is fully closed 3) Right click the task bar icon for Visual Studio 4) Select a solution from the context menu Expected behavior: Visual Studio opens and load the solution without errors Observed behavior: Visual Studio opens and load the solution without errors

                1 Reply Last reply
                0
                • L lmoelleb

                  Unable to reproduce Environment: Visual Studio 2022 version 17.0.3, Windows 11 21H2 Steps to reproduce: 1) Drag an existing solution to the desktop using the right mouse button. 2) Select "Create shortcut here" in the popup menu 3) Double click the created shortcut Expected behavior: Visual Studio opens and load the solution without errors Observed behavior: Visual Studio opens and load the solution without errors

                  Kornfeld Eliyahu PeterK Offline
                  Kornfeld Eliyahu PeterK Offline
                  Kornfeld Eliyahu Peter
                  wrote on last edited by
                  #8

                  That kind of shortcut will open the default VS version. I have 8 of them, at least 3 in daily use, so I have to define the actual exe I want to open and the solution file is command line parameter... So my shortcut is different... Instead target being solution.sln it is path-to-vs-2020-exe solution.sln

                  "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                  "It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox

                  L 1 Reply Last reply
                  0
                  • Kornfeld Eliyahu PeterK Kornfeld Eliyahu Peter

                    That kind of shortcut will open the default VS version. I have 8 of them, at least 3 in daily use, so I have to define the actual exe I want to open and the solution file is command line parameter... So my shortcut is different... Instead target being solution.sln it is path-to-vs-2020-exe solution.sln

                    "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                    L Offline
                    L Offline
                    lmoelleb
                    wrote on last edited by
                    #9

                    And that is why you should always include accurate steps to reproduce when discussing bugs. Everything else just wasting time as there are too many options. Updated steps to reproduce: 1) Search for Visual Studio in the Windows search menu 2) Right click "Visual Studio 2022" in "Apps" 3) Select "Open file location" 4) When Explorer opens, copy the selected shortcut to a new location (I use the desktop) 5) Right click the shortcut and select "Properties" 6) Locate a solution (*.sln file) 7) Right click the solution and select "Copy as path". On Windows 10, you need to hold shift when right clicking 8) In the properties for your shortcut opened in step 5, click the "Target" text box 9) Press "End" on the keyboard (this will take the cursor to the end of the text) 10) type a space, then paste from the clipboard. This will add the solution path to the shortcut. 11) Click OK to close the properties 12) Double-click your shortcut copy to start Visual Studio Expected result: Visual Studio opens and loads the solution without errors Observed result: Visual Studio opens and loads the solution without errors

                    Kornfeld Eliyahu PeterK 1 Reply Last reply
                    0
                    • Kornfeld Eliyahu PeterK Kornfeld Eliyahu Peter

                      It is possible (but not likely) that it is something on my side... I have 8 versions of VS installed side-by-side (too lazy to clean)... However it is the first version of VS does not play nice...

                      "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                      J Offline
                      J Offline
                      Jon McKee
                      wrote on last edited by
                      #10

                      Kornfeld Eliyahu Peter wrote:

                      I have 8 versions of VS installed side-by-side (too lazy to clean)... However it is the first version of VS does not play nice

                      That's impressive. I remember when I installed 2017 with 2015 still installed, if I scrolled too much in the Intellisense suggestions box, it would crash with some out-of-range error (I think that was the error anyway) and Intellisense would be borked until I restarted VS.

                      1 Reply Last reply
                      0
                      • L lmoelleb

                        And that is why you should always include accurate steps to reproduce when discussing bugs. Everything else just wasting time as there are too many options. Updated steps to reproduce: 1) Search for Visual Studio in the Windows search menu 2) Right click "Visual Studio 2022" in "Apps" 3) Select "Open file location" 4) When Explorer opens, copy the selected shortcut to a new location (I use the desktop) 5) Right click the shortcut and select "Properties" 6) Locate a solution (*.sln file) 7) Right click the solution and select "Copy as path". On Windows 10, you need to hold shift when right clicking 8) In the properties for your shortcut opened in step 5, click the "Target" text box 9) Press "End" on the keyboard (this will take the cursor to the end of the text) 10) type a space, then paste from the clipboard. This will add the solution path to the shortcut. 11) Click OK to close the properties 12) Double-click your shortcut copy to start Visual Studio Expected result: Visual Studio opens and loads the solution without errors Observed result: Visual Studio opens and loads the solution without errors

                        Kornfeld Eliyahu PeterK Offline
                        Kornfeld Eliyahu PeterK Offline
                        Kornfeld Eliyahu Peter
                        wrote on last edited by
                        #11

                        Yep - that kind of shortcut... Now I tried from scratch both kind - it opens only once without error (the first try) and than fails with the very same error... Are you on W10 or W11?

                        "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                        "It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox

                        L 1 Reply Last reply
                        0
                        • Kornfeld Eliyahu PeterK Kornfeld Eliyahu Peter

                          So in most part it works well (nothing astonishing in compare to 2019), however I have comfort issue... I have fixed solutions for every project I'm working on. I have shortcuts that open one solution instead of opening VS than pick the solution... I used to it and find it easy to manage and use it since the stone-ages... However 2022 crashes (at System.Windows.Media.Composition.DUCE+Channel.SyncFlush() which may hint something about WPF) using that technique... I can double-click the solution file and it will open... I can open VS and pick the solution - it works... However opening the shortcut crashes... Can anybody check this to see if it is an problem on my computer or happens to everyone (in which case I may waste my time to report a bug that will be close in a month)?

                          "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                          R Offline
                          R Offline
                          Ron Nicholson
                          wrote on last edited by
                          #12

                          Try re-creating your shortcuts. At least one to test. I have a project that I only want to open in VS2019. I created a shortcut to devenv.exe (2019 version) and passed in the sln. It worked fine. I have another project started in 2019 but I created a shortcut to devenv.exe (2022 version) and it also worked fine. So my best guess is to try recreating your shortcut to see what happens. Ron

                          Jack of all trades, master of none, though often times better than master of one.

                          1 Reply Last reply
                          0
                          • Kornfeld Eliyahu PeterK Kornfeld Eliyahu Peter

                            Yep - that kind of shortcut... Now I tried from scratch both kind - it opens only once without error (the first try) and than fails with the very same error... Are you on W10 or W11?

                            "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                            L Offline
                            L Offline
                            lmoelleb
                            wrote on last edited by
                            #13

                            W11 - and no problem opening it multiple times. From what I could google, that error is likely to be driver related. I assume you already checked you have the latest drivers installed.

                            Kornfeld Eliyahu PeterK 1 Reply Last reply
                            0
                            • Kornfeld Eliyahu PeterK Kornfeld Eliyahu Peter

                              So in most part it works well (nothing astonishing in compare to 2019), however I have comfort issue... I have fixed solutions for every project I'm working on. I have shortcuts that open one solution instead of opening VS than pick the solution... I used to it and find it easy to manage and use it since the stone-ages... However 2022 crashes (at System.Windows.Media.Composition.DUCE+Channel.SyncFlush() which may hint something about WPF) using that technique... I can double-click the solution file and it will open... I can open VS and pick the solution - it works... However opening the shortcut crashes... Can anybody check this to see if it is an problem on my computer or happens to everyone (in which case I may waste my time to report a bug that will be close in a month)?

                              "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                              StarNamer workS Offline
                              StarNamer workS Offline
                              StarNamer work
                              wrote on last edited by
                              #14

                              The only error I've found so far in VS2022 is to do with text transformation on build. It works in VS2019, but crashes in VS2022... I've asked about this on StackOverflow but if I don't get an answer will also ask Microsoft. Of course, I use several extensions and one minor annoyance is that either CodeMaid or Resharper (haven't tried to identify which yet) keeps wanting to change some of my namespaces to file scoped when I try to clean it up.

                              namespape xxx
                              {
                              ....
                              }

                              becomes

                              namespace xxx;

                              ....

                              which, of course, breaks the code for VS2019! There's probably a switch to turn it off if I had time to find it...:(

                              1 Reply Last reply
                              0
                              • OriginalGriffO OriginalGriff

                                Ah. I won't be installing that in a hurry then ... I use a right-click on the taskbar to select my project from the "current crop" of pinned projects and it would be a PITA to lose that. It works in Word, Excel, and just about everything else, so why should VS suddenly lose it? Please tell me when that's fixed ... :-D

                                "I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!

                                P Offline
                                P Offline
                                purplemur
                                wrote on last edited by
                                #15

                                I haven't had any issues with opening solutions directly through my pinned solutions in the taskbar context menu. No clue what's going on with OP's issue, though.

                                1 Reply Last reply
                                0
                                • Kornfeld Eliyahu PeterK Kornfeld Eliyahu Peter

                                  I do not know how pinned solution different from a classic shortcut... I have a mac-like toolbar that pops up when I hit the top side of the screen with the mouse. It holds classic shortcuts... Up until VS2019 had no problem with it...

                                  "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                                  K Offline
                                  K Offline
                                  Kirk 10389821
                                  wrote on last edited by
                                  #16

                                  Can I recommend you hard code a fresh new shortcut on the desktop. And open that. See if that works. Then apply that tweak to the shortcuts you are using. Also, do the shortcuts for the OLDER versions STILL function properly?

                                  Kornfeld Eliyahu PeterK 1 Reply Last reply
                                  0
                                  • Kornfeld Eliyahu PeterK Kornfeld Eliyahu Peter

                                    So in most part it works well (nothing astonishing in compare to 2019), however I have comfort issue... I have fixed solutions for every project I'm working on. I have shortcuts that open one solution instead of opening VS than pick the solution... I used to it and find it easy to manage and use it since the stone-ages... However 2022 crashes (at System.Windows.Media.Composition.DUCE+Channel.SyncFlush() which may hint something about WPF) using that technique... I can double-click the solution file and it will open... I can open VS and pick the solution - it works... However opening the shortcut crashes... Can anybody check this to see if it is an problem on my computer or happens to everyone (in which case I may waste my time to report a bug that will be close in a month)?

                                    "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                                    S Offline
                                    S Offline
                                    Steve Naidamast
                                    wrote on last edited by
                                    #17

                                    I am waiting for a few updates to by before I upgrade form VS 2019...

                                    Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com

                                    1 Reply Last reply
                                    0
                                    • K Kirk 10389821

                                      Can I recommend you hard code a fresh new shortcut on the desktop. And open that. See if that works. Then apply that tweak to the shortcuts you are using. Also, do the shortcuts for the OLDER versions STILL function properly?

                                      Kornfeld Eliyahu PeterK Offline
                                      Kornfeld Eliyahu PeterK Offline
                                      Kornfeld Eliyahu Peter
                                      wrote on last edited by
                                      #18

                                      It works only once...

                                      "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                                      "It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox

                                      K 1 Reply Last reply
                                      0
                                      • Kornfeld Eliyahu PeterK Kornfeld Eliyahu Peter

                                        It works only once...

                                        "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                                        K Offline
                                        K Offline
                                        Kirk 10389821
                                        wrote on last edited by
                                        #19

                                        Ah, 2 more questions. 1) If you reboot, does it work the first time again? 2) Create another fresh link. Then create 2 COPIES OF IT! Now try the fresh shortcut. Twice. Confirm the failure Then try one of the copies (only one) Does it work? (I assume not) If it does. compare the 2nd Copy to the first copy and see if the shortcut was modified. It probably was NOT. Next whatever EXE is being run. Go to task manager (after using the first link, the first time, exit VS) and use task manager to KILL any processes linked to the shortcut. Then... see if it works after that. (it shouldn't, since it is the second try). My assumption. The program is not starting up, and is not forwarding on the shortcut parameters. It is already running, and somehow ignoring the parameters!

                                        1 Reply Last reply
                                        0
                                        • L lmoelleb

                                          W11 - and no problem opening it multiple times. From what I could google, that error is likely to be driver related. I assume you already checked you have the latest drivers installed.

                                          Kornfeld Eliyahu PeterK Offline
                                          Kornfeld Eliyahu PeterK Offline
                                          Kornfeld Eliyahu Peter
                                          wrote on last edited by
                                          #20

                                          It is the same driver for VS2019 and VS2022... According to the event log it is about WPF somehow...

                                          "The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012

                                          "It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox

                                          L 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