Hello,
I used LLBLGEN 1.X last year on several projects, quite successfully. It has become my ORMapper of choice.
I am at a new company and I am working on introducing LLBLGEN as an alternative to their current entity framework. The current framework uses basic CRUD stored procedures in MSSQL to populate/save/update very basic entity objects and collection of entities.
Ideally, from a legacy migration point of view, I would like to initially setup my LLBLGEN entities to use the existing legacy stored procedures to populate/save/update the entities and collections, then over time, work on converting the manager classes to using LLBLGen's ORMapping functionality for these operations directly and using LLBLGEN natively for all new stuff of course.
In version 1.X, we did not have projections. I believe I can used projections to populate entity collections based on stored procedures, but does anyone know if there is a way to wire up the individual update/insert/delete operations on an entity to use legacy stored procedures, as a migration step, until the fetch/insert/delete operations can finally be converted to use native LLBLGen generated queries? My problem here is that there is basic business logic encapsulated into the save/update/delete stored procedures that will take a lot of time to convert into the business layer if I have to do it all at once.
Thanks in advance.
Shawn S.
