Behavior in SILVERLIGHT 3.0


This article will give a basic introduction of BEHAVIOR feature in SILVERLIGHT3.0. I will also walkthrough to create a custom behavior.

What is Behavior in SILVERLIGHT 3?

According to definition given in the product introduction of SILVERLIGHT3

A Behavior is in essence a reusable piece of interactivity that can be applied directly to user interface elements in Expression Blend. The whole product introduction on behavior can be read here.

I summarized few of the points as below about SILVERLIGHT behavior

  1. Behavior is new feature introduced in SILVERLIGHT 3.0.
  2. Behavior is a reusable piece of code, which can be attached to any object declaratively.
  3. Behavior is the way to allow designer to add functionality to XAML elements without codes.
  4. Behavior allows attaching functionality to an object without writing any code.
  5. Behavior encapsulates the functionality and can be attached to any element.
  6. Behavior can be attach to an element or object through XAML. There is no need to write C# code.
  7. A single behavior can be attached to any number of objects.
  8. Behavior is reusable piece of code can be attached to any object.
  9. Behavior comes with System.Windows.Interactivity.dll

 Creating a Custom Behavior
Step 1
Create a SILVERLIGHT Application. Two projects will get created SilverLightApplication1 and SilverLightApplication1.Web. If you are not, changing the default name. Add reference of System.Windows.Interactivity.dll in SilverLightApplication1 project.

Step 2

Right click on SILVERLIGHT project and add a class. Give any name, for my purpose; I am giving name ImageBehavior.

  1. Add the namespace using System.Windows.Interactivity;
  2. Inherit class from Behavior<T>
  3. Make T as DependencyObject
  4. Override the methods OnAttached and OnDetaching
  5. On MouseEnter
    event and MouseLeave event write the simple logic to rotate the object to which Behavior will be attached.


using System;using System.Net;

using System.Windows;using System.Windows.Controls;

using System.Windows.Documents;

using System.Windows.Ink;

using System.Windows.Input;

using System.Windows.Media;

using System.Windows.Media.Animation;

using System.Windows.Shapes;

using System.Windows.Interactivity;

namespace BehaviorSample1


public class ImageBehavior : Behavior<DependencyObject>


public ImageBehavior()
protected override void OnAttached()
var ad = this.AssociatedObject as
ad.MouseEnter += (sender, args) =>
var p = new PlaneProjection();
p.RotationZ = new Random().Next();
ad.Projection = p;
ad.MouseLeave += (sender, args) =>
ad.Projection = null;
protected override void OnDetaching()

Attaching Custom Behavior to object

Step 1

Before adding custom behavior to element, we need to add namespaces. Open the XAML page and add below namespaces.


First namespace is for the System.Windows.Interactivity dll and second one is namespace of the custom behavior class.

Step 2

Since; I am going to attach the custom behavior we created with Image control. So for the source of Image control add an image to SILVERLIGHT project by Add an existing item. I have added an image and gave the name a.jpg.

Step 3

Add an Image control on XAML and attach the behavior like below.

<Image Height=”Auto” Width=”Auto” Source=”a.jpg”> <i:Interaction.Behaviors>
<behavior:ImageBehavior />



 Where I isnamespace of dll and behavior is namespace of custom behavior class.


<UserControl x:Class=”BehaviorSample1.MainPage”




xmlns:d=”; xmlns:mc=

mc:Ignorable=”d” d:DesignWidth=”640″ d:DesignHeight=”480″>

<Grid x:Name=”LayoutRoot” Height=”Auto” Width=”Auto” Background=”Black”>

<Image Height=”Auto” Width=”Auto” Source=”a.jpg”


<behavior:ImageBehavior />




 Step 4

There is no need of do any coding in MainPage.Xaml.cs

Run the application

On mouse enter to Image; Image will rotate with random degree of angle. Like below. Thanks for reading.

Dynamic type with Reflection in debug mode


This article will give simple debug mode explanation on how Reflection and Dynamic type works.

Note: Read my previous article on dynamic type here Dynamic Type

Let us create a very simple class called Student.

public class Student{

public void Print(string Name)
Console.WriteLine(“Student Name is “ + Name);

 Now say, you don’t have information about type of the class while creating instance of this class. Or in other words you don’t have type information of the class at the compile time. So how to create instance of this class? Till c# 3.0 ; we had no choice but to take help of Reflection . Code was highly messy. Not very readable and not beautiful either.

Code will look like,

Object student = new Student();

Type studentType = student.GetType();

Object res = studentType.InvokeMember(“Print”, BindingFlags.InvokeMethod,null, student ,new
Object[] {“Dhananjay”});


 Few points about above code

  1. We are creating instance of the Student class as object type. Since we don’t know type of the class at compile time.



By running in debug mode, we can see at compile time class is resolving as DynamicReflection.Student.

  1. In 2nd line of code we are finding, type using GetType method of object class.

We can see Compiler is resolving the type as Student. If you remember Student is name of our class.

  1. On the type (StudentType in our case) we are calling the InvokeMember method to call the method on the instance of the class. InvokeMember is overloaded function and we are passing four parameters to this.
  2. Since method of the class is returning void so res is NULL.



Now if you see above code, is not it very messy? So in c# 4.0 we do have dynamic type to deal with.

dynamic dynamicStudent = new Student();

dynamicStudent.Print(“Dhananjay With Dynamimc Type “);

Now again if you run the above code in debug mode, you will see type for dynamic type is getting resolved exactly the same as of reflection.

After type resolving all the other work to call method is done by compiler at the back ground. So simply we need to call the method on the dynamic type and DLR will take care of everything.


So, we saw in debug mode how dynamic type and reflection works. Thanks for reading.

Returning Large volume of records from SOAP based WCF service


In this article I will explain; How to return large volume of data (around 50000 records) from SOAP based WCF service to any client. I will show; what service configuration setting and client configuration setting is needed to handle large volume of data returning for WCF service.

Follow the below steps,

Step 1: Create a WCF service

.To creates WCF service; select File -> New -> Project-> Web -> WCF Application.

Service will contain

  1. One Operation contract. This function will pull large data from database using stored procedure.
  2. One Data Contract. This class will act as Data Transfer object (DTO) between client and service.
  3. basicHttpBinding is being used in the service. You are free to use any binding as of your requirement.

Data Transfer Class


public class DTOClass

public string SystemResourceId

public string SystemResourceName
public string Created
public string Creater
public string Updated
public string Updater

  1. Name of DTO class is DTOClass. You can give any name of your choice.
  2. There are 6 string properties.
  3. All properties are attributed with DataMember.



public interfaceIService1
List<DTOClass> GetData();

  1. Service is returning List of DTOClass.
  2. To get serialized at run time, making sure Data Contract is known to contract by using known type.

Service Implementation

public class Service1 : IService1{

string cs = @”Data Source=xxxserver;Initial Catalog=Sampledatabase;User=dhananjay;Password=dhananjay”;
List<DTOClass> restDto = new List<DTOClass>();
DTOClass dto;
public List<DTOClass> GetData()
SqlConnection con = new SqlConnection(cs);
SqlCommand cmd = new SqlCommand(“GetAllSystemResourceDetails”, con);
cmd.CommandType = CommandType.StoredProcedure;
DataTable dt = new DataTable();
SqlDataAdapter adp = new SqlDataAdapter(cmd);
for (int i = 0; i < dt.Rows.Count; i++)
dto = new DTOClass();
dto.SystemResourceId = dt.Rows[i][0].ToString();
dto.SystemResourceName = dt.Rows[i][1].ToString();
dto.Created = dt.Rows[i][8].ToString();
dto.Updated = dt.Rows[i][10].ToString();
dto.Creater = dt.Rows[i][9].ToString();
dto.Updater = dt.Rows[i][11].ToString();
return restDto; ;
}} }

  1. This is simple implementation. Where ADO.Net is being used to fetch data from Database.
  2. GetAllSystemResourceDetails is name of the stored procedure.

Note: Purpose of this article is to show how to push large volume of data from WCF service. So, I am not emphasizing ADO.Net part here. See the other articles for detail explanation on ADO.Net

Configuration setting at service side


<service name=TestingLargeData.Service1behaviorConfiguration=TestingLargeData.Service1Behavior>                


<endpoint address=mexbinding=mexHttpBinding contract=IMetadataExchange/>
<behavior name=TestingLargeData.Service1Behavior>                    
<serviceMetadata httpGetEnabled=true/>                    
<serviceDebug includeExceptionDetailInFaults=false/>
<dataContractSerializer maxItemsInObjectGraph=2147483647/>


<basicHttpBinding><binding name=LargeBuffermaxBufferSize=2147483647maxReceivedMessageSize=2147483647>

<readerQuotas maxDepth=2147483647maxStringContentLength=2147483647maxArrayLength=2147483647
maxBytesPerRead=2147483647maxNameTableCharCount=2147483647 />


  1. In service behavior, for dataContractSerializer I am increasing the number of object that can be serialized or de serialized at a time. By default it is set to 3565. Since our requirement is to push or return large volume of data, so I am giving value for maxItemsInObjectGraph to maximum integer number.
  2. Since, I am using basicHttpBinding, so I am modifying values for this binding. I am setting all the attributes to maximum integer value.
  3. Binding I am using is basicHttpBinding.

Compile the service and run to test, whether service is successfully created or not?

Step 2: Creating a client and Consuming the service.

Create any type of client. For my purpose I am creating a console client. After creating a console project, right click at Service Reference and add service reference. While adding service reference make sure, in advance setting as collection type System.Collection.Generic.List is selected.

Configuration setting at client side

<?xml version=1.0encoding=utf-8 ?>

<binding name=BasicHttpBinding_IService1closeTimeout=00:01:00
<security mode=None>
<transport clientCredentialType=NoneproxyCredentialType=None
realm=“” />
<message clientCredentialType=UserNamealgorithmSuite=Default />
<endpoint address=http://localhost:55771/Service1.svc
behaviorConfiguration =r1/>
<behavior name =r1>

<dataContractSerializermaxItemsInObjectGraph =2147483647/>

  1. Attributes of basicHttpBinding has been modified for the maximum integer values.
  2. In endpoint behavior maxItemsInObjectGraph for dataContractSerializer has been modified to maximum integer value.


class Program{

static void Main(string[] args)
Service1Client proxy = new Service1Client();
List<DTOClass> res = new List<DTOClass>();
res = proxy.GetData();
foreach (DTOClass i in res)
Console.WriteLine(i.SystemResourceId + i.SystemResourceName + i.Updated + i.Updater);

In this article, I explained how we can return large volume of data from WCF service and how at client side large volume of data can be consumed. This article explained on WCF SOAP based service. Next article I will explain how to achieve same for WCF REST service. Thanks for reading.