Best Practice for Validation Application Block rulesets to be shared
on client & server?
Hi & Happy Holidays!
We have a Smart Client business app, and, would like to keep the
validation rules on the server side of the SOA.
However, as a performance benefit (i.e. save an unnecessary server
round trip), and user experience benefit, the "on the fly" validation
capability of VAB / Validation Provider / ErrorProvider on the UI
works very well, and we would like to get the benefit of this as well.
Although we can duplicate the rule configs on both Client and Server,
it would be 'nicer' if we can keep to the one common set, i.e. we
would like to keep our entity validation rules in our Server
app.config, but would like to expose a rules 'service' allowing
clients to retrieve these rules (and cache them) for the purpose of
'early / on the fly' validation.
Which brings the question : Is there a simple way to dynamically set
the Validation "rule" store (on the client) to a location other than
app.config, or will we need to hack the file?
This is probably a common scenario with a Smart Client / VAB
combination?
Thanks in Advance
Regards
Stuart
date: Thu, 27 Dec 2007 21:15:10 -0800 (PST)
author: NonNB
