I have a data layer built on Linq-2-SQL in .net 3.5. We are looking at switching to .Net 4. soon. When we started the original development, I was interested in using EF for the data layer, but found that it wasn’t quite an option in .NET 3.5. Now that we are updating, I think about it again.
I understand that L2S is still supported in .Net4, however, I would like to switch to a more active development area for future verification of the system, which is likely to be the main business for a fair time. (My understanding is based on statements such as “We said that we will improve its essence (L2S) and add customer requests where it makes sense, but the focus will be on the Entity Framework.” From Damien Guard in the comments on this post .
What complicates this is that we have introduced several mods to our L2S implementation:
- We tuned the .tt generation file to an honest bit and a bit of L2ST4.
- We use stored procs for all CRUD operations (which we generate automatically), as this allows us to enable / disable verbose audit trail for certain tables as needed.
Most of the rest of what we use, I know, will be fine, because I did it myself in EF4 (actually a lot of it all started in the EF4 database), but I wanted to know if these settings would be appropriate.
So:
- Can we have a customized .tt generation system (or something similar)?
- Can we use our own sprocs for CRUD?
NB: If we were to use EF, I would probably use the version of Database First.
source
share