Just wanted to point out I was looking at the result of a LINQ query last week that was causing a deadlock.

Update [Table] -- Ok

Set [Some Field] = @P1 -- Ok

Where

[Identity Column] = @P2 -- Great!

And [Other Column 1] = @P3

And [Other Column 2] = @P4

-- Stop!

...

And [Other Column 50] = @P52

-- No LINQ! Please, Stop!

...

And [Other Column 150] = @P152

-- What the hell just happened

Unfortunately the programmer couldn't correlate the SQL that was generated to the source of the LINQ code that caused it... so it's still out there. Somewhere. Causing harm.