Managing the whole Database->Entity Model bit is certainly a challenge and I'd welcome a tool to help me manage that process. But for most of my data related development the database and EF model are largely fixed and its the projected models that get overwhelming. With each new "i need this bit but not that" I get a new DTO that needs to be mapped to the EF model and then supported as changes to the core model ripple out to all the projections.
I know "if it did this, I would buy it" isn't that compelling a reason to expend countless dev hours producing a new feature, but I would LOVE it if EntDev allowed you to define DTO's and their projection/mapping from the core data model.
Thanks!
James
Mapping to DTO's
Re: Mapping to DTO's
1. Entity Developer includes the Data Transfer Objects template.
All templates available in Devart Entity Model (*.edml) are described at https://www.devart.com/entitydeveloper/ ... eloper.chm (download, right click > Properties > Unblock), navigate to ORM Support > Entity Framework > Concepts > Model Generation Templates.
2. A current implementation of Entity Developer supports only Database-First and Model-First approaches. Is your request about Code-First (generating *.edml model basing on your *.cs / *.vb classes)?
* If so, please vote for this feature at https://devart.uservoice.com/forums/386 ... evelopment.
* If not, give us an example of the functionality you need.
All templates available in Devart Entity Model (*.edml) are described at https://www.devart.com/entitydeveloper/ ... eloper.chm (download, right click > Properties > Unblock), navigate to ORM Support > Entity Framework > Concepts > Model Generation Templates.
2. A current implementation of Entity Developer supports only Database-First and Model-First approaches. Is your request about Code-First (generating *.edml model basing on your *.cs / *.vb classes)?
* If so, please vote for this feature at https://devart.uservoice.com/forums/386 ... evelopment.
* If not, give us an example of the functionality you need.