CSLA dot NET Version 2.1. Handbook C Sharp Edition by Lhotka

By Lhotka

Show description

Read or Download CSLA dot NET Version 2.1. Handbook C Sharp Edition PDF

Similar programming: programming languages books

Objektorientierte Programmiersprache C++: Vollständige Einführung anhand von Beispielen (VDI-Buch) (German Edition)

In diesem Werk werden alle Aspekte der Sprache C++ behandelt, deshalb ist das Buch ebenso für Einsteiger, mit oder ohne Vorkenntnisse über eine andere Programmiersprache, als auch für Umsteiger von anderen Programmiersprachen bzw. C-Programmierer geeignet. Die Darstellung der Sachverhalte erfolgt knapp und systematisch, die Beispiele sind kurz, prägnant und compiler- unabhängig und auf allen Rechnern mit C++ 2.

Extra resources for CSLA dot NET Version 2.1. Handbook C Sharp Edition

Example text

URI Part Scheme Example rule:// Description Prefix indicating this is a business rule. Host methodName The name of the rule method. LocalPath propertyName The name of the business object property associated with the rule. Query arg1=value&arg2=value A list of extra arguments and their values as provided to the rule method when AddRule() or AddInstanceRule() was called with a custom RuleArgs subclass. Table 7. Uri to parse the values. Uri for parsing, allows you to gain relatively detailed information about the rules associated with the properties of your business object.

Changes to RuleArgs Each rule method can set the severity of the rule as part of its processing. This is important, because some rules might have different levels of “being invalid” based on different conditions. By allowing the rule method itself to indicate the severity of the result, you have a lot of flexibility in how severities are used. A rule method is always passed a parameter derived from the RuleArgs type. 1, RuleArgs now includes a Severity property, and corresponding instance field: public class RuleArgs { // ...

You’ve seen how the BrokenRulesCollection exposes filtered views of the broken rules, and how the IsValid functionality has been enhanced so only Error severity rules make an object invalid. 1, rules may be assigned a priority, which is 0 or greater. Rule methods are invoked in priority order, starting with 0 and climbing to successively higher values. In other words, the higher the number, the later the rule will be executed. Within a priority, the order in which rules are invoked is non-deterministic.

Download PDF sample

Rated 4.50 of 5 – based on 27 votes