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

  1. implement generic repository pattern
  2. separate entities class library
  3. i need odata query support in it
  4. should follow standards (soc , unit of work)

following questions confuse me

  1. database-first approach or code-first approach?
  2. how achieve minimum code?
  3. how can keep track of changes (migration in entity framework?)
  4. how enable odata in it?
  5. 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

Popular posts from this blog

java - SSE Emitter : Manage timeouts and complete() -

jquery - uncaught exception: DataTables Editor - remote hosting of code not allowed -

java - How to resolve error - package com.squareup.okhttp3 doesn't exist? -