Using Entity Framework Code First with or without database generation -


we have couple of large, mature apps installed in hundreds of medical clinics. these apps built using windows forms , wpf , although host database of them, majority of our clients have local install of database.

we in planning stages of rebuilding our application on asp.net mvc platform using entity framework. re-architecting our database, reference, current database has 600 tables , 1900 stored procedures. although don't have official dba, have enough dba skills build , maintain have, capable of designing , building data model ourselves. also, continue have both on-premise , hosted solutions.

our struggle deciding how use ef. we're in agreement should use code-first, of think should build our classes, decorate them attributes, , allow ef generate database us. others think should design , build database , generate code-first pocos.

assuming have non-crud stored procs, triggers, views, stored procs, , user defined functions, database generation reasonable approach? there reasons why might preferred approach? reasons avoiding altogether?


Comments

Popular posts from this blog

php - SPIP: From Tag directly to an article -

jquery - isAjaxRequest always return false -

ruby on rails - In a controller spec, how to find a specific tag in the generated view? -