|
Ok fine, will sit these out since the rules are so strict 
Cheers,
Vikram.
|
|
|
|
|
It is not that the rules are strict, it's more about everyone playing their part. If you want to join in then you need to contribute as well. Why do you think I hardly ever answer?
|
|
|
|
|
Because you canβt figure out the answer?
(Like the rest of us!)
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
Of course. 
|
|
|
|
|
Still do them, its a bit of fun.
What about reacting with a thumbs up if you get it but don't post the answer?
// TODO: Insert something here Top ten reasons why I'm lazy
1.
|
|
|
|
|
Not moronic at all,πππ
|
|
|
|
|
without further comment... The Lounge[^]
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 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
|
|
|
|
|
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 ... 
"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!
|
|
|
|
|
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
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
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.
|
|
|
|
|
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! 
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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!
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
