You should read chapters 1-5 of Expert 2008 Business Objects to get a good understanding of the way the framework supports objects.
In smart client technologies (everything but ASP.NET) the CSLA validation model causes most rules to run on the client. You have to do something specifically different if you want a rule to run on the app server.
In the web things are different. This is because the web technologies are really quite poor for business app development. In the web, your .NET code can't run in the browser - pretty much by definition...
The easiest and cheapest solution is to use Silverlight, because that lets you create a "web app" that is really a smart client.
But if you can't do that, the next best thing is probably to use ASP.NET MVC 2 (which isn't out yet unfortunately), because MVC 2 will automatically project client-side script code into the web page based on validation attributes on your object properties.
And if you can't do that, then you might look at ASP.NET MVC 1, along with one of the open source projects out there that projects client-side script into the web page based on attributes on your object properties.
And if you can't do that, then you'll need to create some ASP.NET Web Forms code to project validation controls into the web form based on the rules defined in your object.
To make this possible, CSLA .NET allows you to ask an object for its list of rules. You'll get back a list of rule:// URI values, and there's a RuleDescription type that helps you parse those URI values into useful information (like System.Uri, but more specialized).
Are you building a Web Forms user interface?
If yes, then you only have two options:
Copyright (c) Marimer LLC