New Posts New Posts RSS Feed: DevForce 6.0 Verification ...
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

DevForce 6.0 Verification ...
 Post Reply Post Reply
Author
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
as123 View Drop Down
Newbie
Newbie


Joined: 27-Apr-2010
Posts: 30 		Post Options Post Options   Quote as123 Quote  Post ReplyReply Direct Link To This Post Topic: DevForce 6.0 Verification ...
    Posted: 27-Apr-2010 at 5:59pm

          The Learning Resources PDF documentation for Validation, 070_Validation, is still referring to the 5.0 version (Object Mapper, VerificationSetterOptions etc.) The Release Notes say it is under construction. Is there a timeframe by which we can expect the latest documentation for the Validation process?

           Is it not possible to set Verifification Interceptor at the Model level and override it using Verification Setter Mode at the Property level? What is the equivalent in 6.0?
 
           Also, in the sample validation application, how do we avoid doing both AfterSet and Instance validation for the same property, without putting in lot of checking in each property verifier method? For example, when the Order Date < Hire Date, the same error message is shown twice (once by AfterSet and another by Instance validation).

Thanks.



Edited by as123 - 27-Apr-2010 at 6:06pm
Back to Top
ting View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 27-Mar-2009
Location: San Francisco
Posts: 427 		Post Options Post Options   Quote ting Quote  Post ReplyReply Direct Link To This Post Posted: 28-Apr-2010 at 6:00pm
You should see significant updates to the documentation in our next release (probably late May).
 
The VerificationSetterOptions has been renamed VerifierSetterOptions.  However, this API is deprecated and we would like to remove it.  Although it was misunderstood, the only intended reason for VerifierSetterOptions was as a performance optimization, and all the logical functionality was available in VerifierExecutionModes.
 
To get the performance optimization, you would now override ValidatePropertyBeforeSet() or ValidatePropertyAfterSet() and not call the base class implementation.  You can also do this in the injected base class if you want to affect multiple types.
I need to talk with one of the architects about your last question, but I wanted to get you the other answers first so you didn't have to wait.
 
Back to Top
ting View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 27-Mar-2009
Location: San Francisco
Posts: 427 		Post Options Post Options   Quote ting Quote  Post ReplyReply Direct Link To This Post Posted: 10-May-2010 at 3:20pm

For the final question, we have discovered that this is a Silverlight DataGrid  bug and we're asking Microsoft about it.  DevForce is only indicating a single error, but the DataGrid displays it twice.  We have duplicated this with no DevForce code and see the same problem with the DataGrid.
Back to Top
as123 View Drop Down
Newbie
Newbie


Joined: 27-Apr-2010
Posts: 30 		Post Options Post Options   Quote as123 Quote  Post ReplyReply Direct Link To This Post Posted: 10-May-2010 at 3:35pm
        Thanks.
Back to Top
ting View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 27-Mar-2009
Location: San Francisco
Posts: 427 		Post Options Post Options   Quote ting Quote  Post ReplyReply Direct Link To This Post Posted: 17-May-2010 at 5:07pm

Ok, we're getting that last problem fixed (with the duplicate messages) for the next release (early June).  Microsoft's implementation didn't quite follow the advertised API, so we are now coding to the actual behavior instead of the documentation.



Edited by ting - 17-May-2010 at 5:08pm
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down