A lot of good articles are doing a great job of explaining LINQ. From syntax to concept and projects, LINQ is well covered. The aim of this article is not to repeat / recycle this material into one big blob. Check out the list of good books for details. My favorite is this little pocket reference.
The concept of this article is based on this short video. This article is a graph of how we reached up to LINQ, and the evolution of C# from 1.0 to 3.5. Is LINQ a new thing or just sweet syntax for old ugly code? In this article, we will look at the journey of C# up to LINQ in less than 10/15 minutes. So let's get started and demystify the LINQ.
We will need some scaffolding code. We will use a City class as follows:
class City
{
private string _name;
private string _state;
public City(string name, string state)
{
this._name = name;
this._state = state;
}
public string Name
{
get
{
return _name;
}
}
public string State
{
get
{
return _state;
}
}
}
Let’s create a collection of cities and then iterate over this collection using foreach as shown below:
List<City> cities = new List<City>();
City c = new City("Santa Ana", "CA");
City c1 = new City("Irvine", "CA");
City c2 = new City("Bloomington", "IN");
cities.Add(c);
cities.Add(c1);
cities.Add(c2);
foreach (City tempCity in cities)
{
Console.WriteLine("City Name : {0} and State : {1}",tempCity.Name, tempCity.State);
}
Let’s filter this collection based on some criteria. Say we want cities from California only. A very simple solution will be to add an if condition inside the foreach loop as shown below:
if (tempCity.State == "CA")
Console.WriteLine("City Name : {0} and State : {1}", tempCity.Name, tempCity.State);
This is a good enough solution. The problem with this code is “tight coupling”. C# 1.0 provided a delegate based composable solution to this problem. The following is the refactored version of this code:
delegate bool IsParticularState(City c);
static bool IsCalifornia(City c)
{
return c.State == "CA" ? true : false;
}
PrintCityInfo(cities, new IsParticularState(IsCalifornia));
static void PrintCityInfo(List
As shown in step 1, we added a delegate IsParticularState. Step 2 is the target method for this delegate. Step 3 is the refactored call to the foreach loop which takes a delegate and cities collection as an input parameter. Step 4 will output the city name and state.
Notice the filter instead of the simple if condition. filter(localCity) is a delegate call. By doing this, we decoupled the filter logic into a separate method:
static bool IsCalifornia(City c)
Still this is too much of a code for implementing a simple filter logic. Wouldn't it be nice if we don't have to add an additional filter method. Yes, that's where C# 2.0 anonymous methods will be helpful. So, the code above can be refactored as follows:
PrintCityInfo(cities,delegate(City ctemp){return (ctemp.State == "CA"?true:false);});
Notice the inline delegate and anonymous method. This is a C# 2.0 feature - anonymous because this method has no name.
This is a good move, but still needs a delegate code. What if we want to improve this code using C# 3.0. Instead of using anonymous methods, we can use lambda expression as follows:
PrintCityInfo(cities,ctemp=>ctemp.State=="CA");
Isn't this code elegant? From 7+ lines, a delegate and a target method call in C# 1.0 to less than half a line of code in C# 3.0. This is the power of lambda expression. Underneath, the compiler is doing all the heavy lifting for us. Lambda expression is a combination of implicit variable and anonymous methods. In our example, ctemp is an implicit variable and ctemp.State=="CA" is an anonymous method.
And now comes LINQ. What if we want to filter the end result on multiple conditions or want to sort the output based on some predefined order like city name? We can do this without LINQ. But LINQ provides an elegant solution for this as shown below:
PrintCityInfousingLINQ(from ctemp in cities
where ctemp.State=="CA"
select ctemp);
static void PrintCityInfousingLINQ(IEnumerable
Here we defined a new method PrintCityInfousingLINQ. This is the same as the PrintCityInfo method. Rather than taking a collection and delegate as an input parameter, PrintCityInfousingLINQ takes enumerator as an input parameter. Another important factor is generics. Generics add the type safety and provide all other well documented benefits.
Let's order the end result by city name. This is a typical order by clause in TSQL. With LINQ, this can be written as follows:
PrintCityInfousingLINQ(from ctemp in cities
where ctemp.State=="CA"
orderby ctemp.Name
select ctemp);
Without the orderby clause, Santa Ana will be the first result. With order by clause, Irvine will be the first record.
From the trivial if condition in C# 1.0 to LINQ in C# 3.0, there is a continuum of logic and syntax. Imagine writing...
from ctemp in cities
where ctemp.State=="CA"
orderby ctemp.Name
select ctemp;
... using if conditions or delegates. LINQ brings the much needed improvement on the syntax front in addition to its support for SQL, XML and objects. With LINQ, intent is closely matched with the language syntax.
At a midnight debate by the empty parking lot of a grad school, someone said something to the effect of –“power of any programming language is its ability to say very complex things very easily. Like The woods are lovely, dark, and deep, But I have promises to keep…”
LINQ is one more step in the right direction. What do you think?
| You must Sign In to use this message board. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
