Databinding with Windows Forms 2.0 - Brian Noyes

Posted on 12/23/2006 @ 12:30 AM in #Books Reviewed by | Feedback | 1972 views

I like to see Brian's book as a perfect complement to mine. He starts where I finished. He talks about about DataBinding, which is a difficult topic to handle. I know Brian personally, and I know that he is a rather smart individual. I know that he finds the most difficult topics, rolls up his sleeves, and dives right in.

Brian's direct and well-organized presentation makes this much misunderstood topic finally understandable.

Disclosure: I was asked by the publisher to review this book.

Sound off but keep it civil:

Older comments..

On 5/16/2007 5:52:13 PM Mike said ..
I am going though Brians Book right now and learning how to use VS2005 and databinding. I haven't made it very far in the book and I got stuck on Chapter 2. The book talks about using the VS2005 Designer to generate the typed DataSet and the TableAdapter. Its simple and it works for my test database. However the one thing that dawned on me is that there isn't too much flexibility in the TableAdapter. It seems like you get one TableAdapter for each DataSet. The problem arises is when you don't know what type of connectivity your users will use to connect to their database. How do you code against that? I mean one customer could use Oledb, another uses Odbc, and the other uses SQL. Does this mean I have to create a DataSet for each connectivity type? I would prefer to use an interface and then cast that into more specific classes after knowing what data connectivity type the user chooses. How do I go about using IDbConnection, IDbCommand, and IDbDataAdapter inside of a TableAdapter? Or am I stuck with creating a DataSet and TableAdapter for each connectivity type?