I'm evaluating LLBLGEN for use in new projects for a client. One of the questions I've gotten from the team is "How is LLBLGEN better than the .NET 2.0 typed datasets and table adapters?"

Personally, I've never liked typed datasets, so I don't use them and am not familiar with these features of .NET 2.0. Can someone who is, answer this question?

Hi jesstedder, I recommend you this readings for convince your team:

http://weblogs.asp.net/fbouma/archive/2004/10/09/240225.aspx http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=5598

here are some of the reasons why I use LLBL

1. Excellent support (and at no additional cost).

2. strongly typed predicates. Predicate expressions (sql where clause) are checked at compile time, not run time, so fewer bugs during testing. the predicate overloads are also nice so they read more like a sql statement then an object. examples:

IPredicateExpression filter = new PredicateExpression();
filter.Add(CustomerFields.CustomerId == 1);
filter.Add(CustomerFields.CustomerId != 1);
filter.Add(CustomerFields.CustomerId > 1);
filter.Add(CustomerFields.CustomerId < 1);

the list goes on, but that gives you an idea.

1. I haven't found a single sql statment that LLBL cannot duplicate

2. the template studio allows you create your own templates (generated code) to work along side LLBL objects. I've dabbled with this, but I know there are others who live and die by this tool. (only available with purchase).

3. with the arrival of v2.1 (beta soon to be released) LLBL is making it easier to develope a business logic tier (not that it's difficult now). Hooks will be provided for auditing and authorizing. The framework already supports validation.