Therefore, this is the first place where the validation should be done.This eliminates the possibility the end-users will incorrectly enter the values.I don't see field validating controls for winform projects like those available in ASP. whenever the user does press calculate I display message boxes mentioning the name of the required fields which are presently empty.When user clicks Calculate, you can check whether the required fields contain required values in expected ranges.Should this validation be done on the client-side or the server-side in a client/side application?Should this validation be done in the business layer or in the middleware component of a multi-layer application?I see your point though and maybe it's just something to get used to.
Comment/question: Was there any design issue with adopting Web Forms validation (awesome), to Windows Forms?
so if you've got some advice/tips that would be greatly appreciated. Checkout is a pretty linear process, but customers never treat it that way, so code must accommodate as much non-linear scenarios possible..still get you back to where you were in a seamless fashion with all the necessary data to process that transaction. I realize I need to get my hands dirtier with all the possible options to do things to get the intended result....
My expectation level (again based on ASP.net) was to simply "wire" a validation control to a templated control in say, a grid column..I know it won't be that way based on what I've gone through so far.... Microsoft is conducting an online survey to understand your opinion of the Msdn Web site.
The refining of the data is done later, when the data is passed to another layer for processing.
Doing so can cause your application or the operating system to stop responding.
Validation means that any data input meets the application requirements in order to ensure consistency and correctness of the data.
There is a deep discussion about when, where and how this validation should be done.
If not you can "Show" message accordingly, instructing the user to enter correct values.
I'll add a code sample in a [email protected] LG that is what i am doing right now! For instance, take the validation controls we have in ASP. I feel the validation controls, since they are positioned right next to the input controls help the user immediately understand what he's doing wrong and thereby give him a better experience.
So basically all these fields need to contain a value in order to perform the calculations.
Additionally, the text boxes should contain numbers - any double values.