Data Binding Anyone?

[Cerebrus]

Hi Tim,

I haven't yet tried VS 2005, (working on VS 2003) and I find that
databinding can make your life real easy, *once* you get the hang of it !

You might be amused to know, that there is a newsgroup dedicated to
Databinding. Try subscribing to :
microsoft.public.dotnet.framework.windowsforms.databinding

Hope you get some useful opinions from the other experts.

Regards,

Cerebrus.

 

[Tim Baur]

I'm a VB6 developer who's just beginning to make the move to .Net 2005, and
I'm wondering if data binding is worth the effort. After a lot of fighting
with it in VB6, I finally realized the best practice was to leave it alone.
It always caused more problems then it solved. I'm guessing that many of
the issues are addressed in VB 2005, but I'm still hesitant to begin
employing it. Any thoughts?

This question is more of a opinion / religion topic, but I'm curious to
know what the group thinks.

 

[Tim Baur]

Hi Tim,

I haven't yet tried VS 2005, (working on VS 2003) and I find that
databinding can make your life real easy, *once* you get the hang of
it !

You might be amused to know, that there is a newsgroup dedicated to
Databinding. Try subscribing to :
microsoft.public.dotnet.framework.windowsforms.databinding

Hope you get some useful opinions from the other experts.

Regards,

Cerebrus.

Thanks, Cerebrus. I'll have to browse the group you mentioned.

 

[CMM]

Databinding in .NET is sheer magnificence compared to the old VB.Classic
days. It was a bit "tricky" in VS2003 because of the weird (slightly hidden)
ContextManager/CurrencyManager objects of the Form that made getting
"Master/Detail" stuff right a bit unintuitive. But this is completely solved
in VB2005 as they pulled out those hidden guys and turned them into full
fledged (and soooo easy to use) toolbox components (BindingManagerSource).

My bit of advice? If you're using datasets, make it a habit to bind to
DataViews instead of directly to Datasets. It simplifies LOTS of things.