Kirk Evans is a Microsoft Architect for the Azure Center of Excellence.
Introduction to SharePoint and Azure IaaS
Building SharePoint Apps with Windows Azure Platform as a Service
SharePoint Solutions and Architectures on Windows Azure Infrastructure Services
Understanding Authentication and Permissions with Apps for SharePoint and Office
This post will show an example of sharing using a Windows 8 app.
I am working on a team project with a requirement to post information to Twitter and Facebook from a Windows 8 app. We started looking at writing our own user interfaces to do this, and then realized this was kind of nuts as Windows Store apps already provide this functionality. If you’ve built Windows 8 apps before, this isn’t going to be earth-shattering, but when I brought it up to the team I realized it was new to many people on the call. Thus, I am writing a quick example.
The opportunities here are really very interesting. Instead of you building all the capabilities for various social networks into your app (post to Yammer, Twitter, Facebook, and more) when that’s not its real function, you can use the share capabilities to defer that to other apps.
Open Visual Studio 2013 and create a new Windows App.
I use the Hub App template as it is really easy to get started with. The other thing I like about this project template is that it contains 3 distinct pages (HubPage, SectionPage, and ItemPage) that we will use to illustrate contextual sharing. As a reminder, here is what the Hub App template generates by default: a hub page, clicking on a section reveals the section page, and clicking an item reveals the item page.
The next thing to determine is how you will share. There are two ways to look at it: the app that is sharing data, and the app that receives data.
I could write the code once and from any page in the app share the same information, however this is so easy I want to complicate things by sharing different information on different pages. I determine that I want my app to share the following information in context:
In each of the following examples, we will share data and show the result.
Let’s start with HubPage.xaml. Edit the page contstructor and add an event handler for navigationHelper.SaveState.
In the LoadState method, there is already some code there. Let’s just add to the existing code. We will use the DataTransferManager type to add a handler for the DataRequested event as illustrated in the diagram above.
Our implementation for the DataRequested event handler is very simple. Obtain the DataPackage from the args parameter, and set properties of the item that is being shared.
When the user navigates away from the page, we don’t want to leave our share registration there, we need to remove it. In the SaveState handler, we simply remove the event handler reference.
The result is very simple. In the charm bar, click the Share charm.
Clicking the Share charm shows the list of apps that are registered to receive this type of data. The title of the item being shared corresponds to the .Title property that we set in our code, and the description corresponds to the .Description property.
We click Facebook and then see the value from the SetText method is shown.
We can do the same for the Mail app or the Twitter app.
Note: If you are getting an error that the request could not be completed or the app is unavailable for sharing, try uninstalling the target app and then reinstalling.
In the preceding example, we shared simple text. Now, let’s share a URL and see what happens. On the SectionPage.xaml page, we follow the exact same pattern: add handlers for LoadState and SaveState, and implement the event for DataRequested,
The implementation for the DataRequested event handler looks just the same as before, but this time we add one property to it to expose a URL using the SetWebLink property.
Just adding that one property to the item being shared has a noticeable effect when the app is run. We get a few more apps that are registered to receive that type of data. Where before we had Facebook, Twitter, and Mail, we now have People, Reading List, and Yammer.
We can now share to the People app to share to our contacts on different social networks.
This time, we are going to add a button to the page to launch the share charm, just because we can.
The pattern is exactly the same as before, so we will show the few lines of code that are different for sharing pictures. When we create the hub app, it contains a folder “Assets” that contains a few sample images. We’ll steal the DarkGray.png file for our purposes here.
That is just ridiculous easy. Let’s run it and see the experience.
So far, we just showed how to send data from our app to a list of apps that are registered to receive different types of data. Now let’s show a quick example of receiving data. The first step is to declare in our app manifest that the app is available as a share target. We can choose different data formats or files. We choose a simple Text example in the app manifest and save.
In app.xaml. we add the following code.
Add a breakpoint on our receiver logic. Run another app, such as Twitter. Select a single tweet and choose Share from the charm bar, and our demo app is now an available target.
The breakpoint is hit and we can see the data that is shared from the other app.
There’s much more to it than this. You can defer the processing of the shared item to a background task, report on success/failure, and more. There are samples and documentation available at Sharing and receiving content to help you get started.
Sharing to Facebook/Twitter from Windows 8/WinRT App
31 Days of Windows 8 | Day #7: Share Contract
Sharing and receiving content