wey97
Jan 28th, 2010, 03:24 PM
I hate designers. Not so much that they're bad...they can be pretty nice to get the grasp of something entirely new like the ADO.NET Entity Framework. Enterprise ORM solutions do not usually involve a GUI or pages of mangled, difficult to understand, auto-generated code.
Everything I've worked with until now has been designed around System.Data.SqlClient populating some form of IEnumerable object whether it be a custom class or something derived from DataSet or DataTable. At least with that you don't HAVE to use the .Net DataSet designer.
How would you go about designing an enterprise solution using the ADO.NET Entity Framework? I've tried to recreate what I can understand from the designer code but it seems nearly impossible.
Everything I've worked with until now has been designed around System.Data.SqlClient populating some form of IEnumerable object whether it be a custom class or something derived from DataSet or DataTable. At least with that you don't HAVE to use the .Net DataSet designer.
How would you go about designing an enterprise solution using the ADO.NET Entity Framework? I've tried to recreate what I can understand from the designer code but it seems nearly impossible.