Results 1 to 2 of 2

Thread: ORM designer bloat

  1. Jan 28th, 2010, 04:24 PM #1
    wey97
    wey97 is offline

    Thread Starter
    Frenzied Member
    Join Date
    Aug 2000
    Location
    Birmingham, AL
    Posts
    1,276

    Question ORM designer bloat

    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.
    Reply With Quote Reply With Quote
  2. Feb 11th, 2010, 03:51 AM #2
    Pino
    Pino is offline
    PowerPoster
    Join Date
    Dec 2003
    Posts
    4,787

    Re: ORM designer bloat

    Enterprise ORM solutions do not usually involve a GUI or pages of mangled, difficult to understand, auto-generated code.
    Why do you need to understand it? It's designed to be run and forgotten about. If you want control over the generated classes why not look at another provider like SubSonic?
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules


Click Here to Expand Forum to Full Width