Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • If you're not tied to a particular DB you might want to look at something like RavenDB. Commented Apr 8, 2012 at 20:50
  • I'm not really averse to using MSSQL, we should be able to migrate bits of it, so we can just scale using Standard Edition, which EC2 supports at a relatively decent rate. Probably would look to Mongo or Couch before Raven, any reason to go for Raven first? Commented Apr 9, 2012 at 21:26
  • 1
    One thing to consider is what you are wanting out of code first. Are you really going for defining your tables in code and having that create the database, or is it the POCO aspect of EF 4.3 that you want? The reason I ask is that you could use POCOs and DbContext with Database First or Model First (you can create a custom T4 to gen the POCOs from your model). The reason I ask is because I sometimes see people writing about "code first", when the thing that they are really after working with POCO/DbContext. Commented Apr 13, 2012 at 16:30