Any experiences with Entity Framework yet?
It sounds like a little more work than using LINQ to SQL, but I’m running into a whole bunch of annoying limitations on LINQ to SQL anyway lately 
Not really. Linq to SQL is good, IMO, only for small and not frequently visited sites. For anything serious or enterprise, custom built objects and stored procedures rock!
I won’t even bother to learn Entity Framework, or Data services or whatever. I don’t know for how long will MS try to bend existing best practices and try to come up with some new stuff which is great, if you are just starting, for RAD.
Only thing that is worth note taking is MVC. That was the way to go from the begining, but Microsoft had to come up with web forms. Does anyone remember that in .net 1.0 and 1.1 by default everything was absolutely positioned on page? Now they are improving with MVC and ability to control your rendered form element names, but it does not mean that everything they create should be taken for good.
Getting rid of stored procedures is one of the primary reasons we’re using LINQ to SQL. There are just too many variations on the same theme to be maintainable.
We have over 700 different stored procedures and to keep them updated and in revision control sucks.
We haven’t upgraded to SQL Server 2008 yet either and a whole bunch of stored procedures need lists of IDs, so you’d end up splitting varchar parameters or adding a finite amount of parameters
So, we’ve started using LINQ to SQL for some of the more obscure, not too heavily used queries. This mixed environment is a bit of a pain as well though.
Any introduction you can recommend to see what Entity Framework could do for us? 