Auto-launching with file and URI associations (Windows Store apps using C#/VB/C++ and XAML)

This topic has not yet been rated - Rate this topic

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

TopicDescription

How to handle file activation

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 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.

How to launch the default app for a file

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.

How to launch the default app for a URI

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.

 

Related topics

Guidelines
Guidelines and checklist for file types and protocols
Reference
Windows.System.Launcher

 

 

Build date: 10/26/2012

Did you find this helpful?
(1500 characters remaining)
© 2013 Microsoft. All rights reserved.