HighTechTalks DotNet Forums  

Best Practice for Validation Application Block rulesets to be sharedon client & server?

Dotnet Distributed Applications microsoft.public.dotnet.distributed_apps


Discuss Best Practice for Validation Application Block rulesets to be sharedon client & server? in the Dotnet Distributed Applications forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
NonNB
 
Posts: n/a

Default Best Practice for Validation Application Block rulesets to be sharedon client & server? - 12-27-2007 , 11:15 PM






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

Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.