Partager via


Tech Ed ’05: Windows Forms: Making the Most of WinForms 2.0 Data Binding

Last week Andrew Brust and I presented a fun session on the enhancements we’ve done for databinding in Windows Forms.  We received a lot of great feedback and had a lot of fun presenting.  Prior to joining Microsoft Andrew and I used to work together as Microsoft RD’s but never presented together.  It was more fun then I would have expected. 
In the session we presented several samples that we didn’t have a lot of time to drill into but promised to post the content:

Session Abstract:

Under .NET 1.x, data binding grew up from a connected 2-tier prototyping tool, to a sensible disconnected, n-tier technology worthy of inclusion in mainstream applications. Under .NET 2.0, consider the ante upped! The design time tools are richer, typed DataSets offer greater encapsulation, UIs can be generated automatically, record navigation is greatly simplified, and master-detail scenarios are handled with ease. You can spend hours with the documentation, designers and Wizards or you can come to this session and learn it all in 75 minutes from Andrew Brust, noted author and speaker on database and data access topics for over a decade.

Powerpoint from Tech Ed '05t 

Powerpoint from Tech Ed WebCast

Samples

Steve

Comments

  • Anonymous
    June 13, 2005
    Your comments in the session abstract come across as sounding ‘elitist’. The implication is that the disconnected model is the right way and the connected model is the wrong way.

    In the real world there are many applications that do simple data access that don’t need the scalability etc. of the connected model and it is still easier (though not using ADO.NET) to produce a connected model solution.
  • Anonymous
    July 28, 2005
    I don't understand why the Customer class doesn't support the IEditableObject interface (begin/cancel/end: edit) but appears to work anyway in the grid?

    When do you need to support IEditableObject?
  • Anonymous
    August 09, 2005
    Hi Chuck,
    IEditableObject is an optional interface. If the interface isn't implemented, DataBinding just won't attempt to call BeginEdit / EndEdit.

    Steve
  • Anonymous
    August 15, 2005
    I've been digging into databinding in winforms 2.0 and haven't had much luck finding anything that did...
  • Anonymous
    November 30, 2006
    Hi, It is very good but also is very complicated for me. Without using the much class is it possible to show as in new article step-by-step method how to acive nested master-details databinding with WinForms 2.0 using VB.NET 2005? I thank you in advance. Kind regards, Niyazi