DZone
Mobile Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Mobile Zone > Launching a Store-Installed App From the Command Line

Launching a Store-Installed App From the Command Line

Starting a normal app from the command line is usually easy, but how are you supposed to start apps installed from the Windows Store when they don't have executables?

Matt Lacey user avatar by
Matt Lacey
·
Jan. 17, 17 · Mobile Zone · Tutorial
Like (1)
Save
Tweet
3.50K Views

Join the DZone community and get the full member experience.

Join For Free

Starting a normal app from the command line (or a script or a scheduled task) is easy. Just start the executable.

However, apps that are installed from the Windows Store don't have executables. So, how do you start them?

The simplest way is if the app has a custom protocol. If it does, then it's just a case of calling start and then the protocol. So, you could do something like this:

start microsoftvideo:

If you want to add a custom protocol to your app, see this link. 

If the app doesn't have its own custom protocol, then you'll have to launch it via the shell. Actually, the shell has its own protocol, so you call something like this:

start shell:AppsFolder\Microsoft.WindowsStore_8wekyb3d8bbwe!App

Here,  Microsoft.WindowsStore_8wekyb3d8bbwe is the PFN (Product Family Name) of the app to launch. Fortunately, these names are easy to find as there are folders with these names for each of the installed apps at  C:\Users\[username]\AppData\Local\Packages.

That folder also includes some things you can't call directly plus some folders that are actually part of other experiences (try start shell:AppsFolder\Microsoft.Windows.SecondaryTileExperience_cw5n1h2txyewy!App) so you can't use everything there.

app Command (computing)

Published at DZone with permission of Matt Lacey, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Flask vs. Django: Which Python Framework to Choose?
  • Change Data Capture to Accelerate Real-Time Analytics
  • Dynamically Provisioning Persistent Volumes with Kubernetes
  • 5 Ways to Optimize Your CQL Queries for Performance

Comments

Mobile Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo