WinRT equivalent of IApplicationActivationManager

[lb90]

In order to activate UWP apps we can use the Application Activation Manager coclass introduced in Windows 8. I wonder if there's a modern WinRT-based replacement API available for launching UWP apps. Thanks!

[castorix]

A way is with AppListEntry.LaunchAsync
You can get AppListEntry from
PackageManager.FindPackagesForUser
Package.GetAppListEntriesAsync

[lb90]

Thanks, that's very helpful!

[DrusTheAxe]

BTW there's also .GetAppListEntries() if you prefer a non-async form, though that's only available since 10.0.19041.0 (version 2004 aka 20H1).

[michael-hawker]

This was a great helper, just wish this was easier to discover/use, had to update my TFM to get access to the APIs.

I guess there's no easy way to get a reference to the spawned process, eh?

[mominshaikhdevs]

I guess there's no easy way to get a reference to the spawned process, eh?

@DrusTheAxe

[DrusTheAxe]

I guess there's no easy way to get a reference to the spawned process, eh?

Only way I know to get the process id of the spawned process is AAM

Or CreateProcess, but that depends

• If the packaged app has an AppExecutionAlias you can CreateProcess("%LOCALAPPDATA%\Microsoft\WindowsApps\alias.exe"...) -- or %LOCALAPPDATA%\Microsoft\WindowsApps...pkgfamilyname...\alias.exe. CreateProcess' PROCESS_INFORMATION should give you the process id and HANDLE
• If the packaged app is installed with an External Location and defines <msix...> in its Fusion manifest then CreateProcess(....extloc...\foo.exe) should activate the app and again, CreateProcess' PROCESS_INFORMATION is at your fingertips

But if you're starting with an ApplicationUserModelID (AUMID) and you need the process id then AAM is the only option I'm aware of.

Why do you ask?

[mominshaikhdevs]

• Launch an installed package with arguments #2142.

• Using IApplicationActivationManager::ActivateForFile does not work for packaged apps #2856.