Receiving shared content (XAML)
[This article is for Windows 8.x and Windows Phone 8.x developers writing Windows Runtime apps. If you’re developing for Windows 10, see the latest documentation]
Sharing is how users connect the content of your app with the people they care about and the apps they use most. If you want to write an app that can receive this content, take a look at the topics in this section.
In this section
| Topic | Description |
|---|---|
Walks you through the steps required to receive shared content from another application. |
|
To receive shared text, your app needs to support the Share contract, handle share activation events, and use the ShareOperation object to retrieve the shared text content. |
|
Links are a common form of data that users want to share. Sometimes the user shares a link directly (such as from an article on a website). Supporting links is also helpful as a secondary option when users are sharing HTML or content that might be available online. |
|
Sharing HTML content is different from sharing other basic formats such as text or a link. HTML content can consist of a variety of content, including text, images, and other information. Here's how your app can receive the HTML content a user wants to share. |
|
Sharing files requires a little more preparation than simpler data types, such as text. When sharing files, you need to consider how long it might take to process the files. |
|
Users want to share content with friends and family as an extension of their computer experience. Apps that embrace this concept create an environment that enables users to share content quickly and effortlessly. You can create an elegant sharing experience by using a custom shortcut called a QuickLink. A QuickLink acts as a link to your app that's customized for a specific set of user actions. |
If you want to supply content for users to share, check out Sharing content.
Related topics
Guidelines and checklist for sharing content