[SOLVED] Windows Forms data binding issue

This is a long standing issue that exists since .NET 2.0 was released. Microsoft didn’t want to solve the issue. You can read a full discussion on the links below.

Windows Forms data binding issue in VS 2005

Windows Forms data binding issue: conclusion

CornStarch – a fixative for Windows Forms Databinding in 2005

In a nutshell, suppose I’m using DataBinding and my business layer decides a given string must be uppercased, say because it’s a family name and in some countries, the family name is uppercased. When I enter the family name in the text box, DataBinding passes the string to the business layer. The business layer changes it to uppercase and notifies the UI layer that there was a change. Every other control can receive the notification but the text box where the name was entered doesn’t receive the notification. Don’t ask why, ask how to solve this awkward behavior.

I attach a triple sample showing this issue in Windows Forms, WebGUI and Wisej. Each sample has two forms, one showing the “normal” behaviour you get from the raw Windows Forms library and another where this issue is fixed. The only difference between the forms is the presence of the BindingSourceRefresh control, the one that fixes DataBinding.

Besides the DataBinding issue, I noticed two other problems:

1. On Wisej, tabbing out of a text box doesn’t trigger Validation (in this case that’s what triggers DataBinding). To trigger it, you must click away of the text box. Tested on Chrome, Firefox, IE and Edge.
2. I dont’ understand why, but I couldn’t ran my Wisej application when the AssemblyName didn’t match the RootNamespace. I don’t know whether this a Wisej issue or a VS2015 issue.