MICROSOFT_PRESS_EBOOK_PROGRAMMING_WINDOWS_8_APPS_WITH_HTML_CSS_AND_JAVASCRIPT_PDF

At the very bottom of this UI you can also set a discrete start page for handling activations, but
typically you’ll use your main activation handler, as shown in js/default.js of the Association launching
sample (leading into js/scenario3.js).
There you’ll receive the activation kind of file, in which case eventArgs.detail is a WebUIFile-
ActivatedEventArgs: its files property contains the array of StorageFile objects from Windows.-
System.Launcher.launchFileAsync, and its verb property will be "open". You respond, of course, by
opening and presenting the file contents in whatever way is appropriate to the app.
Of course, since the file might have come from anywhere, treat it as untrusted content, as we
mentioned earlier for share targets. Avoid taking permanent actions based on those the file contents.
As with the Search contract, too, be sure to test file activation when the app is already running and
when it must be started anew. In all cases be sure to load app settings and restore session state if
eventArgs.detail.previousExecutionState is terminated.
Protocol Activation
Creating a URI scheme association for an app is much like a file type association. In the Declarations
section of the manifest, add a Protocol declaration, as shown in Figure 12-14.
FIGURE 12-14 The Declarations > Protocol UI in the Visual Studio manifest designer.
Under Properties, the Logo, Display Name, and Name all have the same meaning as with file type
associations (see the previous section). Similarly, while you can specify a discrete start page, you’ll
typically handle activation in your main activation handler, as demonstrated in again in js/default.js of
the Association launching sample (leading into js/scenario4.js).
There you’ll receive the activation kind of protocol, in which case eventArgs.detail is a
WebUIProtocolActivatedEventArgs: its uri property contains the URI from Windows.System.-
Launcher.launchUriAsync.
529