Blog from Saravanan Arumugam

Let us talk about Technologies

Category Archives: C#

Identify Nullable Types

I had a need of using the reflection to go through different properties of a class and examine if it is a nullable type.

I have learned an interesting thing that GetType() method upon the property would not let us know if it is a nullable type. Moreover, there is no direct method in reflection to check that up, (like IsVisible or IsValueType).

I found an interesting write up from MSDN that explained the issues I faced and posted a solution to it as well.


How to: Identify a Nullable Type (C# Programming Guide)


The following code lets us know if it is a Nullable type. But before that we need to get the type from non-GetType() way.


                foreach (var property in typeof(Request).GetProperties())
                    Type type = property.PropertyType;
                    //Check the value of non nullable fields
                    if (type.Is.IsGenericType && type.GetGenericTypeDefinition() == typeof(Nullable<>))

User friendly name for Enumeration fields

Unlike class’s properties, showing user friendly display name for an enumeration field is not that easy.

For example, I would like to use the following Enum. But when I display them on screen, I want to display “Prior Record” instead of “PriorRecord”, and “Future Record” instead of “FutureRecord”.

public enum RecordStatus
   New = 0,

   Error = 1,

   PriorRecord = 2,

   FutureRecord = 4,

   ExcessHours = 8,

I tried to use DisplayNameAttribute, but its not applicable to Enums and Fields. So I had to do something equivalent to it.

1. Create Custom Attribute to specify friendly names

First thing to do is to create a custom attribute which I can use to specify the Display Name of each field. We can take advantage of DisplayNameAttribute by deriving the custom type from it. DisplayNameAttribute has all infrastructure already specified. We just need to create a class with constructors.

public class EnumDisplayNameAttribute : DisplayNameAttribute
    public EnumDisplayNameAttribute()
        : base()
    public EnumDisplayNameAttribute(string displayName)
        : base(displayName)

Note that I have placed an AttributeUsageAttribute to make this attribute available for fields.


2. Use the custom attribute on the Enum fields

Next thing to do is to use the attribute to specify the friendly name.

public enum RecordStatus
	New = 0,
	Error = 1,
	[EnumDisplayName("Prior Record")]
	PriorRecord = 2,
	[EnumDisplayName("Future Record")]
	FutureRecord = 4,
	[EnumDisplayName("Excess Hours")]
	ExcessHours = 8,


3. Write an extension method to Enum

Next thing is to show the DisplayName whenever Enum.ToString() is called. We have to write an overload to the ToString() as an extension.

public static class EnumExtension
/// <summary>
/// Shows the user friendly name specified in EnumDisplayNameAttribute
/// </summary>
/// <param name="enumeration">Enumeration object</param>
/// <param name="indicator">An indicator to enable this extension. 
/// Pass any integer as indicator.</param>
/// <returns>User friendly name of the Enumeration</returns>
public static string ToString(this Enum enumeration, bool indicator)
    string returnValue = enumeration.ToString();
    if (indicator)
        //Flagged enumeration will have comma separated value.
        //Split them into multiple values before use.
        var displayValues =
           //Split is made here to handle all the comma separated enum values
            from enumValue in enumeration.ToString().Split(',')
            //Join is made here to work with field object instead of string.
            join field in enumeration.GetType().GetFields()
            on enumValue.Trim() equals field.Name
            select field
                into enumFields
                //If the field has the EnumDisplayAttribute, display it;
                //otherwise, display the regular field name.
                //Conditional output is done through the ternary operator.
                (enumFields.GetCustomAttributes(false).Any(attribute =>
                    attribute is EnumDisplayNameAttribute) ?
                (from attribute in enumFields.GetCustomAttributes(false)
                    where attribute is EnumDisplayNameAttribute
                    select ((EnumDisplayNameAttribute)attribute).DisplayName)
                : enumFields.Name);
        if (displayValues.Count() > 0)
            returnValue = string.Join(", ", displayValues);
    return returnValue;

Note that the ToString() method contains a Boolean indicator. If it is true, the ToString() would return the friendly names else will return the defaults.

The linq statement in the method has 3 levels of loops.

Loop 1. Since the enum is marked with FlagAttribute, the default ToString() may produce comma separated values such as Error, ExcessHours, FutureRecord. So in the linq we split them into an array of strings.

Loop 2. Find the FieldInfo object based on the string we received from the previous loop.

Loop 3. If the field has EnumDisplayNameAttribute, return the DisplayName. If the field doesn’t have the custom attribute, return the FieldInfo.Name.


4. Use the overloaded ToString() method

Now in the places where we need the friendly name, start using the ToString(true).

class Program
    static void Main(string[] args)
            | RecordStatus.ExcessHours).ToString(true));
            | RecordStatus.FutureRecord);


‘__Entities’: type used in a using statement must be implicitly convertible to ‘System.IDisposable’

I have a solution where my working project references the project having the Entity Data Model. When I create the entity model context with the using statement I get the following compiler error.


Error 2 ‘Intrado.Data.MyEntities’: type used in a using statement must be implicitly convertible to ‘System.IDisposable’ C:\Saravanan\MyApp\MyApp.Service.cs 16 13 MyApp.Service


We can find this issue when the entity model is in a different project than the working project. We get this exception since the Compiler knows till the point that the entity class (MyEntities in my example) is derived from ObjectContext. For some reason C# compiler can’t understanding that ObjectContext has implemented the IDisposible.

To resolve it, simply add a reference to the System.Data.Entity in the working project. This should take care of this error.

Facts about Action and Func Delegate

We can notice many methods take Action,Fun or any specific delegate as parameters.

When an Action Delegate or Func Delegate appear, what do they mean? What do they signal to the developer?


Action Delegate

Action delegate, no matter how many parameters it can take, it returns void.

public delegate void Action<in T1, in T2>(
	T1 arg1,
	T2 arg2

There are 17 versions of Action delegates ranging from no type parameters up to 16 type parameters. Action, Action<T>, Action<T1,T2>…etc.

Func Delegate

Func delegate in contrast, always returns the a value of TResult type.

For example, following is the syntax of a Func with nine arguments. This delegate would expect a value of TResult type.

public delegate TResult Func<in T1, in T2, in T3, in T4, in T5, in T6, in T7, in T8, in T9, out TResult>(
	T1 arg1,
	T2 arg2,
	T3 arg3,
	T4 arg4,
	T5 arg5,
	T6 arg6,
	T7 arg7,
	T8 arg8,
	T9 arg9

Like Action delegates, Func has 17 versions ranging from no type parameters up to 16 type parameters. Func<TResult>, Action<T, TResult>, Action<T1,T2,TResult >…etc.

Lambda expressions

A lambda expression can be understood as an anonymous function which can contain expressions and statements. It is one of the key enhancements that C# 3.0 provided to support Linq.

Lambda expressions are useful in all the places where a delegate or expression tree is applicable. In particular, lambda expressions are very useful in the IEnumerable<T> typed objects, which carries extension methods accepting delegate parameter of type Func<T,TResult>.

A lambda expression is written in the following form

parameters => expression/{statements}

Here “=>” is read as “goes to”. Parameter can be a single parameter or group of parameters enclosed within parenthesis.

All the rules of anonymous methods are applicable to lambda expressions. Lambda expressions can be categorized as expression lambda and statement lambdas.

In this paper I am going to present different features of lambda expressions with examples.


Simple Lambda

To square a value, a function has to take the form fn(x) = x * x;

This can be represented as x => x * x in lambda expression.

The following C# code evaluates this function with lambda expression.

delegate long squareValue(int a);


static void Main(string[] args)


    //Simple Lambda

    squareValue squareOf = x => x * x;

    Console.WriteLine("Square of {0} is {1}", 5, squareOf(5));

    //Equivalent ananymous method

    squareOf = delegate(int x) { return x * x; };


Multiple parameters can be supplied by enclosing them in parenthesis. e.g (x, y)

Note: An expression can take zero parameters and can return void.


Lambda calling external method

A lambda can call a external function as follows. The following expression valuates the function fn(x, y) = x² + y.

delegate U expressionDelegate<T, U>(T m, U n);


static void Main(string[] args)


    //Lambda expression calling a method fn(x,y) = x² + y

    expressionDelegate<int, float> expression =

        x, y) => Square(x) + y;


    int a = 8; float b = 5.6f;

    Console.WriteLine("Result of {0}² + {1} = {2}",

         a, b, expression2(a, b));


Square(x) is the external method.


Lambda vs inbuilt System.Func<T, TResult> delegate

Many standard query operations take an input parameter whose type is one of System.Func<T, TResult> family. Func<T, TResult> delegate define the number of input parameters, type of the parameters and the return type. Func<T, TResult> can take up to 16 input parameters and a non void return type.

The last type specified in the Func<T, TResult> is the type of the result or return type.

For example Func<int, float, bool> indicates that this is going to hold a delegate with int and float type input parameters and is going to return a bool as output.

Func<int, int, bool> expression = (x, y) => x == y;
Console.WriteLine(expression(2, 2));



Currying is a function transformation technique with which a function with multiple parameters can be transformed into a series of multiple functions each taking a single parameter.

With currying technique, (x, y) = x*x + y*y is equivalent to x => (y => x*x + y*y )

Here is the C# implementation of the curried function.

//With Currying (x, y) => x*x + y*y is equivalent to x =>(y => x*x + y*y))
Func<int, Func<int, int>> curriedExpression = x => y => x * x + y * y;
int m = 5, n = 7;
Console.WriteLine("Result of {0}² + {1}² = {2}",m, n, curriedExpression(m)(n));

Note the declaration of curriedExpression. The outer expression is said to take the integer as input, and the output of it is another Func<> delegate. This delegate in turn accepts an integer and outputs an integer.

The execution of expression is also a little different from the that of usual expressions. curriedExpression (m) returns a function. Input n is sent to the resulting function to complete the execution.


Statement Lambdas

Statement lambdas take the following form

(parameters) => {statements;}

Any c# statement can be enclosed within the braces and all the paths should end with a return statement, unless the return message is declared to be void.

Let us take the expression to find the largest among 3 integers for discussion.

With the expression lambda we can specify it as

Func<int, int, int, int> greatestNumber = 
         (x, y, z) => 
         (x > y) ? ((x > z) ? x : z) : ((y > z) ? y : z);
Console.WriteLine("Greatest number in the given set is {0}", 
         greatestNumber(15, 6, 11));

The same can be expressed in the statement lambda as

Func<int, int, int, int> greatestNumber = (x, y, z) =>
    if (x > y)
        if (x > z)
            return x;
            return z;
        if (y > z)
            return y;
            return z;

The body of the statement lambda can have any number of statements. However it is recommended to have only a few statements in them say two or three. More than that might affect the readability of the expression.


Lambda inside another lambda

It is possible to have nesting in lambdas. For instance the example of finding greatest among 3 numbers can be expressed as greatestOf(x, y, z) = greaterOf(greaterOf(x, y), z)

The expression greatestOf requires another expression (greaterOf) to be executed within it.

Func<int, int, int> greaterOf = (x, y) => (x > y) ? x : y;
Func<int, int, int, int> greatestOf = (x, y, z) => greaterOf(greaterOf(x, y), z);
Console.WriteLine("Greatest number in the given set is {0}", greatestOf(7, 2, 3));


Variable Scope in Lambda expressions

Lambda expressions can refer to the variables outside the expression within the execution scope. The variables used within the expression would be retained even if the original variable goes out of scope or garbage collected. Here the rule is that the variables in the expression should have been assigned some value before being used.

An example to reflect lambda expression’s treatment of local variables follows.

class LambdaScope
    static Func<string> zeroParameterLambda = null;
    static void Main(string[] args)
        (new MyClass()).DoSomething();
    class MyClass
        public void DoSomething()
            DateTime startTime, endTime;
            startTime = endTime = DateTime.Now;
            zeroParameterLambda = () =>
         Console.WriteLine("Hash code of startTime from lambda expression: {0}", 
         return string.Format("Operation started by {0} and stopped by {1}", 
                 startTime, endTime);
            //Modify the endTime value                
            endTime = DateTime.Now;
            Console.WriteLine("Hash code of startTime from DoSomething(): {0}", 

In the code, you can note that the zeroParameterLambda is defined within MyClass.DoSomething() method. This expression uses the local variables startTime and endTime for its definition. But the zeroParameterLambda is executed only in the Main(). Here the values of startTime and endTime are kept safe to be used in zeroParameterLambda, even though they are out of scope.


I am still exploring on this topic to know more on how the variables are retained and the consideration of garbage collector on these variables. Looking forward to post more papers on this topic.


Lambda recursion

Recursion is the concept of a function calling itself. Recursion is useful in doing mathematical functions on series of numbers, such as factorial, sum/product of a series etc. With lambda expressions, recursion is so handy.

To make the recursion, first declare the Func<T, TResult> initializing it to null. In the next line we can define the expression which can make use of the expression name declared in the first line.

Here is an example of lambda recursion to find a factorial a number and to check if the number is prime or not.

//Factorial of n or n!
Func<int, int> fact = null;
fact = x => (x == 0) ? 1 : x * fact(x - 1);
int a = 6;
Console.WriteLine("{0}! is {1}", a, fact(a));
//Check prime number
Func<int, int, bool> prime = null;
prime = (x, y) => (y == 1) ? true : (x % y == 0 ? false : prime(x, y - 1));
Func<int, bool> isPrime = x => prime(x, x / 2);
int b = 2011;
Console.WriteLine("{0} is a {1}prime number", b, (isPrime(b)?"":"not "));


Use of Lambda expression

Lambda expressions are introduced to primarily support the Linq in C# 3.0. However lambda expressions are applicable to variety of places. Let me present a few uses of lambda expressions.


Use of Lambda expression in place of Predicate<T> and Action<T>

Lambda expressions can be used in the old style List.FindAll<T>/ConvertAll etc. where the parameter is of type Predicate<T> or Action<T>.

List<int> numberArray = new List<int> { 1, 4, 3, 2, 6, 7, 9, 13 };
Console.Write("\nOdd numbers in the array");
numberArray.ForEach(x => { if ((x & 1) == 1) Console.Write(" " + x); });
Console.Write("\nMultiples of 3 in the array");
numberArray.FindAll(x => x % 3 == 0).ForEach(y => Console.Write(" " + y));


Use of lambda expression as event handlers

Lambda expressions can be used as simple event handlers.

For instance in the following code snippet, I have used the lambda expression as a handler for Console.CancelKeyPress event.

A little background about the code snippet; following console application would start printing from 0 to 10000 sequentially. While printing, the operation can be interrupted by pressing Ctrl+C in the middle. This would terminate the current console operation. Before termination, the CancelKeyPress event would be triggered. So with the following code in place, we can see a custom message before console operation gets terminated.

Console.CancelKeyPress += 
    new ConsoleCancelEventHandler(
        (object obj, ConsoleCancelEventArgs e) => 
                 Console.WriteLine("Console is about to break...")
for (int i = 0; i < 10000; i++)


Use of lambda expression in IEnumerable<T> extension methods

IEnumerable<T> provides a variety of extension methods to support Linq. There are many extension methods that would accept lambda expressions in place of Func<T, TResult> delegate family.

Here is an example.

var myObject = new[] {
                   new {Name = "Saravanan", Age = 20},
                   new {Name = "Thomos", Age = 18},
                   new {Name = "George", Age = 25}
var filteredObject = myObject.First(obj => obj.Name.StartsWith("S"));
Console.WriteLine("Filtered Output: Name={0}, Age={1}", 
         filteredObject.Name, filteredObject.Age);


Use of lambda expression to do operations in a different thread

The following sample does a file operation in a different thread while the main thread continues to work on something. The main advantage of this technique is that the sub thread has full access to the local variables of main thread. It would be a real delight for those who have experienced the difficulty in passing objects between the threads.

string textToBeWritten = "Some sample text";
Thread t = new Thread(new ThreadStart(() =>
    using (Stream stream = File.Create(@"C:\Temp\somefile.txt"))
        StreamWriter sw = new StreamWriter(stream);
        lock (textToBeWritten)

Note that the textToBeWritten is a variable outside the scope of the sub thread, but still the sub thread has complete control over it.

Note: Care should be taken to use these variables in a thread safe way. Use of lock{} can help.



Lambda expression is a great value-add to .Net languages. While the lambda expression provide the flexibility and short cuts to coding, it comes with the cost of readability. So the recommendation is to limit the use of lambda expression with a clear consideration of readability and maintainability. In every other sense, lambda expression should be a favorite for developers.


Reference materials

Lambda Expressions (C# Programming Guide)

Anonymous Methods (C# Programming Guide)

Where to use Lambda Expression

Lambda calculus