It seems like EF is all the rage these days. I'm just starting to play with it myself. After getting bitten by that LINQ-to-SQL disaster I wanted to wait to see if this technology was going to make it. Anyway, EF seems to make it fairly easy to model your business classes. Does this technology replace CSLA? With data annotation we get rudimentary business rules. Should I just use straight EF or should I wrap EF entities with CSLA objects? It seems like double work re exposing all of those props again in CSLA. I've used CSLA.net for years now. Traditionally my dataportal methods talk straight ado.net to sql server. I've played with a couple of projects where we exposed data through a REST web service and the CSLA classes were modified to make http calls running the dataportal in 'local' mode. Anyway, I'm just reaching out for guidance and opinions on this.
↧
