Feature: Support `Files .` to open current path from cli

[NightWatcher314]

What feature or improvement do you think would benefit Files?

For example, I can use "files.exe ." to open files.app in current path. Just same as "explorer.exe ." .
I don't know is there any cli.

Requirements

• Post some clis

Files Version

3.1.0.0

Windows Version

10.0.22631.2861

Comments

No response

[yaira2]

Launching using Files . is not supported yet, but if you set Files as the default file manager, running explorer . will open Files with the current path.

[NightWatcher314]

I have set files as my default file manager and restart my computer. But when i use explorer . or explorer.exe . in terminal, it still open win11's file manager.

[NightWatcher314]

I have set files as my default file manager and restart my computer. But when i use explorer . or explorer.exe . in terminal, it still open win11's file manager.

OK, I have found the problem. When I use powershell, it won't work well, but cmd does.
Can you add support to powershell? Thanks.

[yaira2]

👍

[saikotek]

@yaira2

I tried to invoke Files from either Powershell or cmd and I noticed that the method Files.App.OnActivatedAsync() is called with the ILaunchActivatedEventArgs type instead of the ICommandLineActivatedEventArgs type and the latter is the one that you'd expect and that contains current directory path.
According to this: https://learn.microsoft.com/en-us/uwp/api/windows.applicationmodel.activation.commandlineactivatedeventargs?view=winrt-22621 application should define AppExecutionAlias which is already defined in Package manifest.

I'm not sure what could be causing it.