-
To Bind or not to Bind
That is the question. Anyone have experience binding to custom objects? Should I do it or populate forms manually. I searched the previous posts and not to much information was available.
I am doing a rather large project and want to decide on a method early on.
Thanks!
-
I hate binding. I hated it in vb6 and I hate it in .NET
its much safer and foolproof (IMO) to do it manually and populate controls based off of objects returned from data access classes. Now I do bind data grids to datatables and stuff, but for text boxes, etc. i do it manually
txtFoo.text = someObject.aProperty
and so on.
-
I hate binding too... I wouldn't bother if I were you. Apparently its pretty good with webforms, but as a windows app developer, Ive had problems with it, so I don't bother.
-
I think .NET took a whole big step forward in the binding department being able to bind to classes but I still find that I don't use it that much, maybe its just old habbits. I almost always do for small things or read-only lists but for actual editing of decent sized objects I usually rely on events and just property assignment.
-
From what I have dug up on other forums points to the same conclusion.
Thanks for you input guys!