>>>That combined with having to manually add Stored Procedure code in multiple places after each generation of the EF code put me right back to doing things the simple way (at least after I got away from Silverlight).
>>>
>>
>>
>>... and that simple way would be ... (for the rest of us :) )
>
>I use stored procedures and functions to simplify the calls I have to make from a application (and to add security). Then I use plain old SQLCommands, DataReaders, etc to do my database work.

I use stored procedures and functions too, but the datareaders have been replaced by strongly typed datasets and the commands have been wrapped in classes and methods.
90% of my code involves extensive manipulation of data in datatables and if you saw the way I type (it's ugly), you'd understand why I'll never give up Intellisense on the data fields.
The framework I use (based largely on Bonnie's blogs) does most of the CRUD with one-line commands, so EF, while it looks elegant, offers relatively little at this point.