Home/ Questions/Q 480777
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T00:55:39+00:00

i’m under the impression that EF with POCO: allows you to map your own

  • 0

i’m under the impression that

  • EF with POCO: allows you to map your own POCO’s to the entities on the model (.edmx).
  • EF Code-Only: no edmx / model designer (ie. CSDL/SSDL/MSL (collectively EDMX) metadata). Still POCO’s but the mappings, relationships, navigation, etc are all manually coded (hence the code-only, description).

If this description of the two concepts is (more or less) correct, why would someone what to do a Code-Only instead of EF with POCO?

Both are doing POCO’s, but the 2nd one has the extra burden of having to also do the mapping, manually?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team
    1. Code only is great if you want to write the mapping by hand without having to slog through XML. Also the edmx designer gets unwieldy after 50 or so models, it’s just a burden to use that way.

    When something goes wrong inside your mapping XML its really a PITA to dig around in the xml to make the fixes you need. Also the designer breaks if you start manually editing your xml in certain scenarios.

    Now I don’t know the details but the designer in EF1 didn’t support all the available mapping options. The EF4 designer has some improvements ( one way relationships come to mind ) but I’m not sure if it has feature parity with manual mappings.

    1. Yes.
    • 0