Comments by rayden54 (Top 4 by date)

Do you still use a repository layer with Entity Framework or not? I seem to be finding contradictory info in that regard (it might just be that some of it's outdated)?

I asked about EF partly because that's what I was researching before I asked the question, but also because everything I'm finding for ADO.NET and repository pattern seems to be for MVC.

Why ADO.NET instead of Entity Framework?

I honestly don't know. It used to do a one-way upgrade and then would throw a bunch of errors. Now, it's opening up fine (not upgrading). It'll build and run, but it's like the database just doesn't exist. It's doing the same thing in VS 2010.