Code First Entity Framework

Sign in to leave a comment.

• 

  Gowtham Rajamanickam11y agoPosted Mar 14, 2015, 4:50 AM

  good..
  • 

    Suraj Sahoo11y agoPosted Mar 14, 2015, 9:10 AM

    Thanks a lot Gowtham :)
• 

  Sam Hobbs11y agoPosted Jan 14, 2015, 10:23 PM

  Software design typically has requirements definition, system design and implementation phases followed by a couple more phases. Which approach is more consistent with that? Would the Code First approach be more consistent or would the Database First or Model First approach be? Which do DBAs prefer/use?
  • 

    Suraj Sahoo11y agoPosted Jan 14, 2015, 10:30 PM

    Thanks Sam for putting up a good question here, Code first Database First approaches are great to be approached with the expertise in concern. Like you have an existing database then it is always wise to use DB first approach and also if you are a good DB designer. :) When your code defines the database i.e. Code First approach, you need be careful as a minor change on the DB level would be lost since it is defined by code. Plus point in Code first approach is the POCO entities are not auto generated as in DB first you have your own code that can be manipulated unlike the autogenerated code.
  • 

    Suraj Sahoo11y agoPosted Jan 14, 2015, 10:32 PM

    There is also an interesting EF version coming up EF7, which is "CODE FIRST ONLY" please follow the following link to get a brief on that. http://blogs.msdn.com/b/adonet/archive/2014/10/21/ef7-what-does-code-first-only-really-mean.aspx Thanks again Sam.