MM .NET Application Framework


Product Details

 

MM .NET Business Rule classes tracks two types of errors:
  • Broken business rules
  • Application warnings

Broken business rules (such as required fields that are empty) prevent data from being saved. In contrast, a warning is simply a message that can be displayed to the user as a word of caution, but still allows data to be saved. For example, you may want to warn the user that, although a specific piece of information is not required, if they don't enter this information then something may go wrong.

The beauty of having business rules enforced in the business layer is that rules are enforced the exact same way in both Windows and Web applications.

Displaying Broken Rules and Warnings in Windows Applications

The default method for displaying broken rules and warnings is by means of the .NET Error Provider in Windows applications (in WPF applications a red box is drawn around the "problem" user interface control). The Error Provider displays a warning icon next to each user interface control associated with a broken rule:

You can also choose to display broken rules and warnings in a dialog. For example:

In addition, you don't have to write ANY code to display broken rules or warnings in your applications--MM .NET completely takes care of it for you.

Although a few default implementations are provided for you, the way broken rules and warnings are displayed to the end user is completely configurable to suit your needs.

Displaying Broken Rules and Warnings in ASP.NET Applications

The default method for displaying broken rules and warnings in Web Forms is similar to that found in Windows Forms. When a broken rule or error is encountered, an error icon is displayed next to the user interface control associated with the error:

As with Windows Forms the way broken rules and warnings are displayed to the end user can be easily configured to suit your needs.

Back to Feature List