Welcome to the Lounge

OriginalGriff15-Dec-21 20:57

OriginalGriff

15-Dec-21 20:57

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 ... Big Grin | :-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 Peter15-Dec-21 21:06

15-Dec-21 21:06

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

Jon McKee15-Dec-21 21:50

Jon McKee

15-Dec-21 21:50

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.

lmoelleb15-Dec-21 21:11

15-Dec-21 21:11

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

purplemur17-Dec-21 4:04

purplemur

17-Dec-21 4:04

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.

Super Lloyd15-Dec-21 20:59

Super Lloyd

15-Dec-21 20:59

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! Smile | :)

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

Kornfeld Eliyahu Peter15-Dec-21 21:10

15-Dec-21 21:10

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

Kirk 1038982117-Dec-21 5:45

Kirk 10389821

17-Dec-21 5:45

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 Peter18-Dec-21 6:41

18-Dec-21 6:41

It works only once...

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

Kirk 1038982118-Dec-21 11:19

Kirk 10389821

18-Dec-21 11: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!

lmoelleb15-Dec-21 21:09

15-Dec-21 21:09

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 Peter15-Dec-21 21:16

15-Dec-21 21:16

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

lmoelleb15-Dec-21 21:32

15-Dec-21 21:32

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 Peter15-Dec-21 22:10

15-Dec-21 22:10

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

lmoelleb16-Dec-21 7:54

16-Dec-21 7:54

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 Peter18-Dec-21 20:22

18-Dec-21 20:22

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

lmoelleb22-Dec-21 0:44

22-Dec-21 0:44

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.

Ron Nicholson16-Dec-21 7:02

Ron Nicholson

16-Dec-21 7:02

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.

StarNamer@work17-Dec-21 1:28

StarNamer@work

17-Dec-21 1:28

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... Frown | :(