EF - CodeFirst.... not so much.

[Dave Kreskowiak]

The database it makes is actually very straight forward and easy to follow, at least if going the CodeFirst route. It creates the tables and fields with names mirroring your classes almost exactly the same. The differences being where relationships come in. In that case, a name will always have the format ClassName_ClassProperty for FKs. It really doesn't "put everything everywhere".

A guide to posting questions on CodeProject[^]
Dave Kreskowiak

[Dave Kreskowiak]

Wow. My experience goes back 6 months, and I find that it definitely does NOT "put everything everywhere", at least on the database side. It puts everything where I would expect it to, but then again, I'm not a DBA by trade. But, if you were talking about where EF CodeFirst code goes, then it does get a little wild. Updating the Context(s) with DbSets takes a bit planning and documentation to keep straight, as well as your own custom Initializers, Models, wrapper classes (UnitOfWork), ... But, I've put all of that in its own project to keep it organized. Though, I agree with your assessment of the Configuration API. It's a bit difficult to wrap my brain around it, but I've managed to get an 80 table database running without too much of a headache, using about 25 explicit relationship configurations in four classes. One table has 18 relationships going to it but I only had to manually configure seven of them. But, as with every framework that relies on Convention to write code and automate tasks for you, it's no different than any other in its complexity.

A guide to posting questions on CodeProject[^]
Dave Kreskowiak

[R Giskard Reventlov]

Used it on a large project and a few smaller ones but now gone back to ADO.

"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. Those who seek perfection will only find imperfection nils illegitimus carborundum me, me, me me, in pictures

[Nicolas Dorier]

I am using ADO.NET + data contract serialized blob approach. That way, queries stays close enough to SQL. And I have some flexibility to change data format without impacting the table structure, and existing clients, thus making deployment easier. Also, I get the benefit of intellisense on the data in the blob column. :) That said, EF code first is cool for doing websites without messing up with SQL. But sometimes messing up with SQL is the simplest way. (And in my case, it is often the case)

[George H Slaterpryce III]

In this instance I had one table that had entries that multiple other tables had one to many relationships with. They way EF mapped this out was... interesting, and less than efficient. for example CustomerAddresses VendorAddresses Instead of having just a CustomerID and AddressID in another table, had the whole of the address class stored in each of these tables, instead of one single address table. There are other cases. and this case was something that can be overcome, but it's just a pita.

[Mycroft Holmes]

If the naming of a FK is the worst it does then I don't see the problem. Personally I'm a data structure first builder, I have trouble conceiving of a code first application. Considering 90% of my work is based on LOB massaging of huge chunks of data I guess this is understandable. I still won't entertain the idea of Ef in our apps!

Never underestimate the power of human stupidity RAH

[George H Slaterpryce III]

I've never hosted an application on the cloud. But Codefirst doesn't support migration so I would be interested to see how it would be easier.

[George H Slaterpryce III]

Problem is, I'm relatively new to EF / CF. It's a technology I just don't use in my normal day to day development. The technology seems to be trending high enough that I should probably become more familiar with it. The project I'm working on now is a bootstrap project. One of those projects you have to do every once in a while to keep up with current practices. I'm constantly fighting the little gremlin on my shoulder screaming "Why are you doing it this way?!, it would take you five friggin minutes to do it the old way!". Because if I didn't I would never keep up. Now, after I feel comfortable enough with the tech, I might not use it again, but until I learn it well enough that I could Teach (Which is a looooooooong way away) it. I'll hold off final judgement.

[Rutvik Dave]

George H. Slaterpryce III wrote:

But Codefirst doesn't support migration

It certainly does[^]. :) (...or we are not talking about the same thing.)

Remind Me This - Manage, Collaborate and Execute your Project in the Cloud

[George H Slaterpryce III]

Huh, all the books and documents I've been reading said it didn't.... cool! thanks for the info.