This one’s going to be long, but for those of you who’ve felt the first 3 in this series were too easy I promise this one’s tougher J.
LINQ at its core requires any data source to be queryable, which basically means it must implement IEnumerable. (It’s actually a bit more complicated than that, for a full explanation see section 11.21.2 of the Visual Basic 9.0 Language Specification).
Recently I got a customer question about how to use LINQ to Dataset in an .aspx file. The compiler was complaining that it couldn’t find the AsEnumerable method that allows LINQ to work over a DataTable (“AsEnumerable is not a member of ‘DataTable’”).
All – I’m about to go on for my LINQ Deep Dive and Tips &Tricks session at VSLive in San Francisco. I posted all demos & slides here:
Yesterday I promised to post about the hidden gems in Visual Basic and Visual Studio 2008 that you haven’t read about in blog posts or seen at conferences. I forgot that I mentioned a few of my favorite features in the Beta1 announcement where I showed off the improvements in the Intellisense experience –
I escaped from Redmond this week to present at VSLive Orlando on LINQ in Visual Studio Orcas. As promised, please find the slides and demos included as an attachment below.
As mentioned during the talk – that was intended to be an overview.
This is the sixth installment in my series of posts about extension methods. You can find links to the rest of the series here.
Today I am going to talk about some best practices for using extension methods.
This is the 5th installment in my series of posts about extension methods. You can find links to the rest of the series here. Originally I had planned on discussing extension method versioning issues, but I’ve decided to postpone that topic to my next post and talk about extension methods and generics instead.