-
Notifications
You must be signed in to change notification settings - Fork 7.1k
workspaces: shell:appsfolder launch does not support the command line #39433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
{ | ||
Logger::trace(L"Launching {} as {}", app.name, app.appUserModelId); | ||
auto res = LaunchApp(L"shell:AppsFolder\\" + app.appUserModelId, app.commandLineArgs, app.isElevated); | ||
auto res = LaunchApp(app.appUserModelId, app.commandLineArgs, app.isElevated); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously, if it launch with "shell:appFolder\" way, actually the comandLineArgs mean nothing since it doesn't support passing any app's args..
NOTE: I don't mean it need to be investigate or fix anything in current PR, I mean with this fix, it may, not sure if there must be, open a possibility to support "args" in case a particular steam://XXX support args as part of this URL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sense, will take a look afterwards
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes a regression in launching Steam games by restricting the scope for shell:appsfolder launches when command line arguments are not supported. Key changes include introducing a Steam protocol prefix constant and modifying the launch logic for apps with an appUserModelId.
- Added a new constant for Steam protocol detection.
- Updated the launch condition and logic to directly launch Steam games without prepending "shell:AppsFolder\".
Comments suppressed due to low confidence (1)
src/modules/Workspaces/WorkspacesLauncher/AppLauncher.cpp:139
- There is an inconsistency in referencing the Steam protocol prefix. A new constant 'SteamProtocolPrefix' was introduced, yet this line refers to 'NonLocalizable::SteamProtocolPrefix'. Consider updating the reference to use the newly declared constant.
if (!launched && !app.appUserModelId.empty() && app.appUserModelId.contains(NonLocalizable::SteamProtocolPrefix))
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
…#39433) shell:appsfolder launch does not respect the command line
…microsoft#39433) shell:appsfolder launch does not respect the command line
Fix #39427
Summary of the Pull Request
Fix a regression when supporting steam games launch in workspaces by this PR #38380

Try to launch steam game with shell:\appsfolder/appusermodelid
When doing release check, use terminal as the "command line testing app", that works fine, so missed this one.
This pr restrict the scope of specific launch case for steam games
PR Checklist
Detailed Description of the Pull Request / Additional comments
Validation Steps Performed
Locally verified for edge and visual studio, and make sure steam games still work
#39427