27. February 2013 19:24
Just saw Julie Lerman show a slick way to set the modified date on an entity by overriding the SaveChanges() on a DbContext:
Other good tips:
- Download the EF PowerTools for a nice plug in that lets you rt-click on the class that implements DbContext and select EF\View Entity Data Model (read only) => to get a relational diagram of how EF is going to create your database before you do a migration.
- In your models, use both the navigation property and the foreign key to increase performance (w/out FK, EF has to go figure out what ID to put in there), to make some object graph management more intuitive for adding/updating or just figuring out if that navigation property exists without invoking lazy loading.
- For lookup-lists, you can improve performance by not tracking the entity state:
When you do the AsNoTracking, combine it with the previous tip so that EF doesn't add a new MyEntity when you save the parent each time:
parent.MyEntityId = Id; // instead of parent.MyEntity = myEntity <- that might cause EF to save a new (duplicate) myEntity to the database
25. April 2012 16:27
This isn’t quite a cheat sheet, but it is a quick reference to the workflow for using EF Database Migrations.
I’m also using MvcScaffolding on my controllers with the –Repository flag to stub out my controller, views, and repository.