Entity Framework: code first – model first [bookmark]

A short bookmarks list on Entity Framework “code first – model first” and final NUGet Gallery link (for Entity Framework 5;) )

• Model-First in the Entity Framework 4
• Code-First Development with Entity Framework 4
  EF 4.1 Code First Walkthrough

• [EF 4.1] When is Code First not code first?
• entity Framework NUGet Gallery (EF 5.0.0 rc 🙂 )

Hope it helps!

Technorati tags: EF, Entity Framework

SQL Server Replication and Entity Framework

When setup database merge replication, rowguid columns are added to every table automatically, identity cannot be used as primary key in this replication.
This rowguid column has default value, so your app doesn’t need to be updated … but, in EF you can update model from database schema, then all these rowguid columns are imported … and EF will raise error build. 😦

Column MyTable.rowguid in table MyTable must be mapped: It has no default value and is not nullable.

The quick&dirty solution is: edit .edmx file, and delete all rowguid columns, and everything related.

A better solution is to write an EF add-in extension, in order to filter away rowguid columns …
unfortunately, I can’t provide any link because can’t remember where I read that tip 😦
here is a post: Error 3032 during EF 4.0 validation  ,  last reply by JendaPearl
hope it helps! 😉

Technorati tags: SQL Server, Entity Framework

Entity Framework and GUID primary key

Moving Primary Key from Int Identity to UniqueIdentifier (… Guid) it’s a big deal.

Before you decide, better listen more than one voice 🙂
Here is once more: sing a GUID as an EntityKey in Entity Framework 4

😉

Technorati tags: Entity Framework, Guid

Entity Framework: “Unable to determine a valid ordering for dependent operations. Dependencies may exist due to foreign key constraints, model requirements or store generated values.”

Just for example:
refactoring some stored procedures, in order to get a simpler store procedure mapping,
combining ADD and UPDATE stored procedures in just one sp.

Field ID (int, identity(1,1)) as input parameter, and RETURN value, different by scopes: RETURN value only in ADD mapping,
both ADD ad UPDATE having ID as input parameter.

First tests failed, with this message: “Unable to determine a valid ordering for dependent operations. Dependencies may exist due to foreign key constraints, model requirements or store generated values.” .

Removing ID returned value in ADD action cleared the message, but it was necessary to auto-generate ID. 😦

Technorati Tags: Entity Framework.