oauth - Web Api with Entity Framework code-first or database-first? -
this might big question. me out come out of this.
i developing web api oauth (facebook, google). have database might undergo further modifications.
i need
- implement generic repository pattern
- separate entities class library
- i need odata query support in it
- should follow standards (soc , unit of work)
following questions confuse me
- database-first approach or code-first approach?
- how achieve minimum code?
- how can keep track of changes (migration in entity framework?)
- how enable odata in it?
- how have generic repository?
is there way implement entire api in database-first approach , convert code-first approach?
scaffolding api controller odata not simplify work in case of odata support, if how have generic dbcontext
, generic repositories.
Comments
Post a Comment