ॐ

I never said, won't need help, neither I said, you won't help, its friendship that we share, asking help is too rare, I know before I need it, you would always be there, you would always be there. our frindship may stale, and those memories may ail but am assured my pal, you would be there when rest may fail, you talked like a bro, with skills of a pro, never get tired, of teaching me to grow i trust you and i know before I need you my bro, you would hared like a hare as you would always be there, you would always be there. I promise before you ask for it, ...I would always be there, I would always be there,

I have been toying with data binding in .net for quite some time now. And ever since I started working and analyzing the binding support in .net f/w 2.0, I have always been eager to know: What makes WPF data binding so great that Microsoft showcased it as the biggest driver for WPF and MVVM? Even though the data binding existed in .net framework 2.0, why didn't MS pushed for its use as it did for WPF? The INotifyPropertyChanged interface was introduced in .net framework 2.0 and was fully supported by WinForm binding engine. However, most of my fellow developers are unaware of this fact.  So the fundamental question that arise is why should one go for WPF if all we want is nice Data Binding support and it’s available in .net 2.0? The answer to this question is, MS has introduced an all new Data Bindinding engine in WPF which fixes lots of bugs of WinForm data binding, has a much improved performance. And I think this is enough for any GUI developer to consider switching to WPF