Skip to main content
Software Engineering

Return to Answer

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
Community Bot
Community Bot
  • 1

I assume by EDMX you mean Database First or Model First rather than Code First (POCO). You can still do code first with POCO's with an existing database if that's the reason for using EDMX.

However if you're absolutely stuck with an EDMX you can use POCO data transfer objects as a wrapper around the EDMX to isolate it from your BLL and top UI. This question about the same subjectThis question about the same subject on Stack Overflow discusses this alternative.

I assume by EDMX you mean Database First or Model First rather than Code First (POCO). You can still do code first with POCO's with an existing database if that's the reason for using EDMX.

However if you're absolutely stuck with an EDMX you can use POCO data transfer objects as a wrapper around the EDMX to isolate it from your BLL and top UI. This question about the same subject on Stack Overflow discusses this alternative.

I assume by EDMX you mean Database First or Model First rather than Code First (POCO). You can still do code first with POCO's with an existing database if that's the reason for using EDMX.

However if you're absolutely stuck with an EDMX you can use POCO data transfer objects as a wrapper around the EDMX to isolate it from your BLL and top UI. This question about the same subject on Stack Overflow discusses this alternative.

Source Link
Turnkey
Turnkey
  • 1.7k
  • 9
  • 10

I assume by EDMX you mean Database First or Model First rather than Code First (POCO). You can still do code first with POCO's with an existing database if that's the reason for using EDMX.

However if you're absolutely stuck with an EDMX you can use POCO data transfer objects as a wrapper around the EDMX to isolate it from your BLL and top UI. This question about the same subject on Stack Overflow discusses this alternative.