VS 2022
-
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
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.
-
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
-
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
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...:(
-
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 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
-
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
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
-
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?
It works only once...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
-
It works only once...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
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!
-
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.
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 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
VS2022 and VS2019 will not send 100% identical commands with 100% identical data with 100% the same timing to the driver. So one program running fine while the other doesn't will not clear the driver of any wrongdoing. And since it is WPF that runs the UI in VS, it will look like it is "about WPF somehow" if your driver is doing the wrong thing. But just to be double clear: I did NOT - repeat - NOT - write "this is a driver issue". I googled the error. Read a few links. Driver issues where mentioned. Basic on the information available I can't say if the error is in the driver, the Windows graphics layer, WPF, or Visual Studio. But you can't either, so you should not conclude "VS2022 is broken" due to this. One hint though: If you have MSI Afterburner installed, try uninstalling it. It injects itself into the driver, and it has killed my rather simple WPF based program before.
