ImplicitDataTemplate is a new feature in Silverlight 5. Using ImplicitDataTemplate, you can declare multiple Data Templates for your control and based on the data type, you can load the proper data template automatically.

In this article we will discuss on the same step by step with a good example. Read the complete article to know it in depth. Do you have any queries, let me know. Feedbacks are always appreciated.

Introduction

Let's have a quick analysis of what we want to achieve to showcase this feature. Assume, we have an organization where we have Employees as well as Customers who are related to the organization. Now, we need to store records of both employees and customers. At the end, we need to display the records showing them in proper way.

To demonstrate, we will create a ListBox and there we will mention whether the person is an employee or a customer. This simple example will help you to understand the feature very easily.

Prerequisite

Before starting with the rest of the topic, you need to set up your development environment. You need Visual Studio 2010 with SP1,Silverlight 5 BetaTools for Visual Studio 2010. Later you need to create a new Silverlight project.

Find the below posts, which will answer all your queries and help you to set up your prerequisite:

InstallSilverlight 5 Betain your development environment. You can install it side-by-side with the existing Silverlight versions

Once your dev environment is set up properly, jump to the next step to start discussing on the main topic. Don't forget to ask your queries at the end of the articles.

Setting up the Solution

Before starting describing the feature with an step-by-step example, we need to set up the solution in proper way. Once you created the project, create the directory structure in MVVM way. Remember that, MVVM structure is not require to use this feature but I prefer working in MVVM pattern.

In the solution explorer, first create the folder structure. For our MVVM based sample, we will create "Models", "Views", "ViewModels" and "Services" folder as shown below:

Once, your folder structure is done, let's create the classes and xamls in proper location. Add MainView.xaml in Views folder, MainViewModel.cs in ViewModels folder, DataService.cs in Services folder and an interface called IPerson.cs in the Models folder. Now create two classes named "Customer.cs" and "Employee.cs" in the same Models folder and implement them from the IPerson interface. Expose some properties in IPerson interface and implement them in both Customer and Employee class.

Once done, build your project and fix the issues that you encountered.

Interface Implementation

Let's declare some properties named Firstname, Lastname and Age in the interface. Here is the implementation of the same:

Model Implementation

Implementing the DataService

You need a DataService to return the Person details. A person may be an Employee or a Customer. Assume that, we are fetching it from database in this step and returning to the client. Here we will hard code the collection and return it back. We added few Employees and few Customers in the collection. As the base interface is IPerson for both the classes, we can easily add them in the collection. Find the code snippet here:

For your reference, you can download the DataService class from here: DataService.cs

Implementing the ViewModel

Let us start coding on the ViewModel. Implement the INotifyPropertyChanged interface in it, so that, once any property changes it will notify the view automatically to refresh the same. Now create a property named "Persons" of type ObservableCollection<IPerson> as shown below. In the constructor, call the GetPersons() method of DataService and store the data records in the property named "Persons".

You may want to download the MainViewModel.cs file. Download it from here: MainViewModel.cs

View Implementation

It's time to create the view and bind the collection to a listbox. First of all, add the namespaces of Model and ViewModel as shown below. We need to use them while binding data. Now, in the UserControl.Resources, add the MainViewModel as a StaticResource.

Add a ListBox and set the DataContext of the ListBox to the MainViewModel instance. Also, bind the ItemsSource property of the ListBox to the Persons collection which is present in the MainViewModel.

Here is how we created it:

Once done, build your project once again and fix the errors if any.

Creating DataTemplate in Older Way

Let us think in the older way of DataBinding using the DataTemplate. Either we create it in the Resource dictionary and set the binding as StaticResource in the actual control, or, we add the template directly inside the control. Both are similar way. Let's go with the second approach to understand easily.

We need to add the ItemTemplate of the ListBox first before adding the DataTemplate. Inside DataTemplate we create the template which we want to display and we do proper data binding before displaying any content.

Here is the older way to implement it:

Note that, here we will see the same output, if we run the application. Because, we have a single DataTemplate to display them. We can't add multiple DataTemplate to the control based on the Data Type. Ohh!!! Alternative approach is creating two or more DataTemplate and load them dynamically from the code behind based on the data type. But that will not resolve our problem too. Using this approach, you can't mix the items of various data types in a single control. You need to handle it from the code behind as a workaround which is very tricky.

So, how to handle this in simple and effective way? Microsoft recently launched the Silverlight 5 Beta which has a feature called ImplicitDataTemplates. Our article title is also on the same topic. Using this you can easily do it in proper way. How to do it? Let's start using the feature now and understand it very clearly.

Creating Implicit Data Types

Using Implicit Data Types, you can use multiple data templates for a single control instance and display the data accordingly in proper fashion. We will use the same DataTemplate that we used in the previous example.

Remove the existing DataTemplate if you already added it inside the ListBox. Now, in the resource dictionary, copy the same template two times and change the display text accordingly. In our first template, we will set it as Employee and in the second template we will set it as Customer.

As per the new feature guideline, you need to specify the DataType of the DataTemplate. For the first template add the DataType property as Employee and for the second use Customer as the DataType property.

Have a look into the below code snippet for understanding it very easily:

Demo

Now it's time to see it in action and understand the actual behaviour. Let's build and run the application. You will notice that, it uses proper DataTemplate for proper Data Type. Check with the collection that we received from the DataService and match with the data in the UI. You will find them similar.

From this, we can understand that, it loads the proper DataTemplate from the resource based on the data type. No need to bind the template to the control directly. Just place it in the resource dictionary and it will pick it directly from there based on the data type.

What Next?

Last but not least, I always welcome your feedbacks about my article. Please add a few comments at the end of the article and support me delivering more good content to you. Thank you for reading my articles and visiting my blog. I also tweet. Follow me on Twitter @kunal2383.

If you have come this far, it means that you liked what you are reading. Why not reach little more and connect with me directly on Twitter, Facebook, Google+ and LinkedIn. I would love to hear your thoughts and opinions on my articles directly. Also, don't forget to share your views and/or feedback in the comment section below.

About Me

Kunal Chowdhury is a Windows Platform Development MVP of Microsoft, a Telerik MVP, Nokia Developer Champion, Speaker in various Microsoft events, Author, passionate Blogger and a Software Engineer by profession.