CPU5005 Exam Revision Entity Framework Approaches Quiz

1. Changes can be more easily rolled-back if necessary (4, 5)
6. Changes to the database made directly won’t be reflected in the model/application logic at all and can cause serious problems/undetectable or difficult to detect bugs (4, 5)
7. Any change on database side easily reflected on code model side by updating the .edmx file (as simple as telling VS to refresh/update the file while displaying it) (8, 5)

1. Clean, non-auto regenerated POCOs (plain old class objects) (4, 5)
2. Dealing with some database objects (stored procedures etc.) can make things more difficult than with database-first (4, 5)
3. Typically used for new applications against legacy (existing/old) databases (8, 5)
4. Often faster development than with Database-First (4, 5)
8. Can be laborious and complicated to create models for large databases (4, 5)
9. Model classes are created first, then ORM creates the database automatically from them (4, 5)
10. Changes to database may break application once models are updated in code without there being obvious reasons why (database design normally sits outside of source control, so change control can be difficult) (8, 5)

Get Revising