Random thoughts about development on the Microsoft platform
This week I ran a quick training session at SSW on ASP.NET Dynamic Data. I used the Developing Data Driven Web Applications Using ASP.NET Dynamic Data session that David Ebbo did at MIX08. Some nice take aways from this are:
Just a quick tip for those of you working with LINQ and WCF.
LINQ-to-SQL natively supports lazy loading as long as your entities are still managed by the DataContext. However, when you pass your entities across WCF your entities become detached from the DataContext so you can’t lazy load on the client side - which makes perfect sense.
The question is how do you then pass a LINQ entity and its child collections across WCF?
This is where the DataLoadOptions class comes in handy. This class allows you to specify exactly what child collections to load along with your entity.
Without this you would have to make two service calls - one to get the parent object and another to get the child collection.
Nice little time saver here, to declare a trivial property (just sets and returns a private variable) all you need to do in .NET 3.5 is:
public string FirstName { get; set; }
This syntax looks exactly like how you would declare an interface or abstract property. Previously you would have to write code like this:
One little known and scarcely document feature of LINQ is its Aggregate method. This function is very useful when you want to do something to the whole collection.
Lets say I have the follwoing BlogEntry class
public class BlogEntry
{
public Tags { get; set; }
}
Now what do I do if I want to build a tag cloud?