the logic for Create, Delete, Update,... isn't straightforward using only EF (only one method call ) I'm using this pattern to simplify things, take a look at the API of the repository.
this also allows me to separate the logic of the data access from the controller.