I thought the point of LINQ was to make writing queries in-line with C# easy. That doesn't seem to compute if most developers need to use a third party tool to help them with creating LINQ statements. If LINQ is not easier to develop and has none of the advantages of stored procedures, then why should I consider using it instead of T-SQL in stored procedures?

LINQPad is a tool for experimenting and trying out LINQ queries. It can greatly speed along your coding as you can immediately see the results. A good comparison point is regular expressions. When I'm using a regular expression, many times I'll just code up a quick JavaScript app to test out the expression. Having it separate from my application allows me to more readily test with all varieties of data.

I unfortunately did not get the seminar email notice until today (the seminar was yesterday). I am hoping there will be a replay available.

I, too, received the email notice after the seminar. Please schedule a replay.

Sorry about the confusion.

I passed along the notice from O'Reilly because I thought some of my readers might be interested. I posted it as soon as I knew about it, which was too late for last week's newsletter. This week's newsletter went out after the Webinar happened.

I have no control over the Webinar and no affiliation with O'Reilly. You might want to contact the speaker. The appropriate Web site is

http://www.albahari.com/nutshell/

If you had been reading my blog or my RSS feed instead of relying on the weekly newsletter, you'd have known about the Webinar in plenty of time.

-- martin