Databinding: Good idea?
Posted on 2004-08-13
I've had a lot of experience with Data binding with VB6. One hard lesson I learned from it is that it can save a lot of development time in the beginning, but as soon as you need to do something outside of its expected use (example: try allowing the user to select the database to use - the ADODC control connects to the design time db before allowing you to change the connection string) you get totally screwed.
I'm starting a new project with C# and I'm wondering if similar limitations exist. One major difference is the visibility of design-time objects that can be edited at run-time, so that's good. But I'm too new to C# to know if any problems lurk. I was wondering what the C# community thought about databinding? Is it safer to assign values to controls (ie: text box) manually?