Nice articles series about caching of the datacontext from linq to sql or entityframework. It follows the logic series of steps a developer will take in learning how to use this, and then how to write tightly coupled code as a result. I have seen so many poor examples of using the datacontext in asp.net apps, this is quite refreshing to see someone attack the problem from where most novices leave it (tightly coupled) and move it to a more elegant design solution.

So that means maybe 250,000 per day in reality? Becuase I know I have downloaded it AT LEAST 9 times when I visit the MS site. It keeps saying I don't have it and must download it again... grrrr

yuck, I would shoot anyone on my team who nested 5+ ternary operators. If you want to get rid of the IF ELSE lists replace it with another construct, not a shortcut to the exact same construct.

I agree, nothing here to see about .net - move along...

Good job Mike! That looks really awesome.

Rather than just pointing to a 2 paragraph blog entry that points to another article - just kick the actual article. Makes it easier and more relevant to the community.

Great article - Lots of good examples of ways other culture information can break your code. Good examples and text to explain the reasoning for the code.

You need more ads on your site! 2 paragraph article with 12 dozen ads and banners - feh

As someone who has had to implement DNS MX lookups before I can tell you this library will save you a TON of effort and reading through RFCs. I downloaded the library and it appears to be very well thought out and written. DNS Lookups for SPF are included as well, very cool.

Very cool to see ES supporting Mono as well!

Yea, and so should cars and houses - SOCIALISM! That is what we really need!

This link is now broken - how to remove a post from dot net kicks?

Holy cow, he was young to have died. I just saw him last year at a show. Sad day for sure.:(

lol - I had to read it just for the title! :D

Nice, I didn't know you could chain them.

Custom LINQ providers are going to be a big deal eventually. Right now I think everyone is just trying to get their head around LINQ period. Well written article, and I am sure a lot of people will reference in the coming weeks and months.