Open in 'Visual Studio' select wrong IDE version

fork-dev / TrackerWin

Bug and issue tracker for Fork for Windows

451 stars 10 forks source link

Open in 'Visual Studio' select wrong IDE version #2127

Open Tognolo opened 5 months ago

Tognolo commented 5 months ago

I've installed on my PC both VS2019 and VS2022. I've setted in Windows settings the 2022 version as default application. I've this situation:

when I double-click on .sln file, it's opened with VS2022;
When I use the "Open in 'Visual Studio'" option inside Fork, some projects are opened with VS2019, others with VS2022.

I tried to delete the .vs folder, but the behaviour doesn't change. How can I tell Fork to use the default VS version?

DanPristupov commented 5 months ago

Fork uses vsselector to run .sln files. You can ensure that in the log. The log is located at %localappdata%\fork\logs\fork.log

I don't know how vsselector works, but looks like it uses data in the .sln file: https://stackoverflow.com/questions/11042636/how-exactly-does-visual-studio-version-selector-chooses-a-visual-studio-versio

S-Tasker commented 5 months ago

This seems to break when you have versions of Visual Studio installed that are not licensed (I.e. 2019 vs. 2022) in this case. I have specifically set *.sln files to open with Visual Studio 2022 in Windows 11, but Fork tries using VS2019 unfortunately.

Is there a way this could be changed as a toggleable item? For example: "Use VSSelector (Default)" or "Use windows file association preferences"

pfaustinom1 commented 4 months ago

I'm facing the same problem as @S-Tasker, Fork keeps using VS2019 even if Windows 11 is set to open VS2022 by default.

pfaustinom1 commented 1 month ago

Any news about this? I'm facing the same problem.