You can use the association launching API to launch the user's default app for a file type or protocol. You can also enable your app to be the default app for a file type or protocol.
In this section
| Topic | Description |
|---|---|
|
Windows allows an app to register to become the default handler for a certain file type. Both, desktop apps and Windows Store apps can register to be a default file handler. If the user chooses your app as the default handler for a certain file type, your app will be activated every time that type of file is launched. | |
|
How to handle protocol activation (Windows Store apps using JavaScript and HTML) |
Windows allows an app to register to become the default handler for a certain URI scheme name. Both desktop and Windows Store apps can register to be a default handler for a URI scheme name. If the user chooses your app as the default handler for a URI scheme name, your app will be activated every time that type of URI is launched. |
|
Learn how to launch the default app for a file. Many apps need to work with files that they cannot handle themselves. For example e-mail apps receive a variety of file types and need a way to launch these files in their default handlers. | |
|
Learn how to launch the default app for a URI. URIs allow you to launch another app on the system to perform a specific task. For example, if you want to allow the user to send a mail to a contact in your app you can use the mailto: URI to launch the user’s default e-mail app. | |
|
By understanding the relationship between Windows Store apps and the file types and protocols they support, you can provide a more consistent and elegant experience for your users. |
Related topics
- Sample
- Association launching sample
- Reference
- Windows.System.Launcher
Build date: 10/26/2012
