Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
I hate it too. I use EF to connect to the data but build the db and code separately. I find that is not harder to do it that way and you have total control.
-
@zeprod I design and create the database tables first, then I create the model classes based the database tables. Add Database.SetInitializer<MyStoreContext>(null);
to Application.Start. This keeps visual studio from running entity migrations. I keep my db context real lean, mainly just using it to map my model classes to my database classes. For large apps I create query and command classes otherwise I just query db context in the controller actions. I have an example on github https://github.com/dtinsley333/....
Related Rants
Fuck entity framework code first! It's a pain in the ass making relationships work with code first! 😑😑
undefined
.net
entity framework