In our previous Windows Phone 7 tip, we learnt how to search applications and/or music in the WP7 marketplace using the MarketplaceSearchTask
API.
Today in this post, we will learn about the MarketplaceHubTask
API to launch the Windows Phone 7 Hub client in your phone device. Using the code, you can also launch it in the phone emulator. Continue reading to learn more about it.
Know About the API
“MarketplaceHubTask
” is a launchers task which allows user to launch the marketplace hub client and display the marketplace items in the screen. You can customize the API to search either Application or Music contents by providing the MarketplaceContentType
property as shown below:
public enum MarketplaceContentType { Applications = 1, Music = 2 }
If you specify the ContentType
of MarketplaceSearchTask
as Application, it will show only applications and if you specify Music, it will show only music.
Code and Demo
Now it’s time for us to see the code and demo. Let us first demonstrate the use of the Application
content type to launch the hub client with only applications. The following code implements the same:
var marketplaceHubTask = new MarketplaceHubTask
{
ContentType = MarketplaceContentType.Applications,
};
marketplaceHubTask.Show();
Here is the screenshot of what you will see when you execute the above code:
If you want to launch the client for music, you need to change the ContentType
as shown here:
var marketplaceHubTask = new MarketplaceHubTask
{
ContentType = MarketplaceContentType.Music,
};
marketplaceHubTask.Show();
Calling the Show()
method actually executes and launches the proper screen of the Hub
client. Here is the screenshot of the Music screen:
Hope this small post was helpful for you to understand the use of the API “MarketplaceHubTask
”. Stay tuned to my blog, facebook and twitter for many more articles, news and tips on Silverlight and Windows Phone 7.
Reference: http://www.kunal-chowdhury.com.
You may like to follow me on Twitter @kunal2383 or may like the Facebook page of my blog http://www.facebook.com/blog.kunal2383.