I have mixed feelings about LINQ. I don't want it interfering with my database, and running queries against it so I think I'll be sticking to stored procedures for this type of access. However, there are also cases where I think it is very useful.
Here's a blog post from my friend Christiaan Baes on an useful implementation of LINQ to order directories by creation date:
http://blog.baesonline.com/2008/01/17/OrderingDirectoriesByCreationDateUsingLinq.aspx
Edit: As Fabrice pointed out in one of the comments below, it's really DLINQ that I'm saying I'll be avoiding, and not other LINQ methods.
Today I found a strange bug in IE7. If you have an unordered list, and you specifically give a height to each li element, the numbers reset themselves so each number ends up being "1"! Try this out!
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"><html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Test</title> <style type="text/css"> ol li {height:40px;} </style> </head> <body> <ol> <li>This</li> <li>is</li> <li>just</li> <li>a</li> <li>test</li> </ol> </body>
</html>