Take a convenient look at what App Connect sends your app when you extend the Search experience. This sample app displays the App Connect URI parameters when launched from the various quick cards: product cards, place cards, and movie cards. Learn more about the types of values that are associated with various search terms, and how to access those values from your app. For step-by-step info about how to develop an app like this, see How to: Extend Search with App Connect for Windows Phone.

You need to install Windows Phone SDK 7.1 to run this sample. To get started, go to the Windows Phone Dev Center.

Using the Quick Card sample

This app is designed to help you explore live quick cards. In this section, you search for products, movies, and places that are associated with the extensions in the application manifest file. After locating a quick card, you launch your app to see the parameters that were passed to the application from the App Connect deep link URI.

Launching the app from a quick card breaks the debugging connection. For more info, see the Debugging the Application section in How to: Extend Search with App Connect for Windows Phone.

Important Note:

This sample requires an internet connection from your PC or Windows Phone device.

To view product card URI parameters

  1. Press F5 to debug your application and deploy it to the emulator or device.

  2. After the app loads, tap the hardware Search button to open Bing.

  3. In Bing, enter a search term that is related to a product, such as a video game console name. For example, “xbox 360” will return product cards related to Xbox 360 consoles. To test a product card with the Bing_Products_Video_Games extension, two things are required:

    • Bing must consider the search term to be relevant to video game products.

    • Product cards that are relevant to the search term must already exist at Bing and be associated with the Bing_Products_Video_Games extension.

  4. On the web pivot page, select a product under the products heading. This will launch the quick card related to the product.

    Tip:

    If you do not see the products heading, try a different search term or add an additional product extension to the WMAppManifest.xml and Extras.xml files. For a complete list of search extensions, see Search registration and launch reference for Windows Phone.

  5. On the quick card for the product, swipe over to the apps pivot page and tap on the app titled Display URI Parameters. Note that the caption reads Product URI Details.

    Note:

    If you do not see an apps pivot page, the particular product card is not associated with any of the product extensions listed in the WMAppManifest.xml and Extras.xml files. Tap the Back button and try a different search term.

  6. After tapping the app in the apps pivot page, observe that the QuickCardTargetPage.xaml page displays the parameters in the App Connect deep link URI for the product.

To view movie card URI parameters

  1. Press F5 to debug your app and deploy it to the emulator or device. This step is optional if you have already deployed the app.

  2. After the app loads, tap the hardware Search button to open Bing.

  3. In Bing, enter a search term that is related to movies, such as “movies”, “movies in theaters” or the name of a movie playing near you. To view the parameters from a movie card with the Bing_Movies extension, two things are required:

    • Bing must consider the search term to be relevant to movies.

    • Movie cards that are relevant to the search term must already exist at Bing and be associated with the Bing_Movies extension.

  4. On the web pivot page, select a movie listed in the search results above the web heading. This will launch the quick card related to the movie.

    Note:

    If you do not see movies listed above the web heading, try a different search term. There are no additional extensions available for movies.

  5. On the quick card for the movie, swipe over to the apps pivot page and tap on the app titled Display URI Parameters. Note that the caption reads Movie URI Details.

  6. After tapping the app in the apps pivot page, observe that the QuickCardTargetPage.xaml page displays the parameters in the App Connect deep link URI for the movie.

To view place card URI parameters

  1. Press F5 to debug your app and deploy it to the emulator or device.

  2. After the app loads, tap the hardware Search button to open Bing.

  3. In Bing, enter a search term that is related to a location. For example, for food and dining locations, use a search term such as “food” or the name of a restaurant near you. To test a place card with the Bing_Places_Food_and_Dining extension, two things are required:

    • Bing must consider the search term to be relevant to a food and dining location.

    • Place cards that are relevant to the search term must already exist at Bing and be associated with the Bing_Places_Food_and_Dining extension.

  4. On the local pivot page, select a food and dining location under the map that is displayed. This will launch the quick card related to the place.

    Tip:

    If you do not see results on the local pivot page, try a different search term. For a complete list of search extensions, see Search registration and launch reference for Windows Phone.

  5. On the quick card for the place, swipe over to the apps pivot page and tap on the app titled Display URI Parameters. Note that the caption reads Place URI Details.

    Note:

    If you do not see an apps pivot page, the particular place card is not associated with any of the place extensions listed in the WMAppManifest.xml and Extras.xml files. Tap the Back button and try a different place card.

  6. After tapping the app in the apps pivot page, observe that the QuickCardTargetPage.xaml page displays the parameters in the App Connect deep link URI for the place.

Note:

This sample is packaged as a Windows Phone 7.5 project. It can be converted to a Windows Phone 8 project, by changing the target Windows Phone OS version of the project. To create a Windows Phone 8 project, you must be running the Windows Phone SDK 8.0 on Visual Studio 2012. You can download the latest version of the SDK from http://dev.windowsphone.com/downloadsdk.

To convert the sample to a Windows Phone 8 project:

  1. Double-click the .sln file to open the solution in Visual Studio.

  2. Right-click the project in the Solution Explorer and select Properties. This opens the Project Properties window.

  3. In the Application tab of the Project Properties window, select Windows Phone OS 8.0 from the Target Windows Phone OS Version dropdown. A dialog will appear asking if you want to upgrade this project to Windows Phone OS 8.0.

  4. Select Yes to upgrade the project.