none
IValidatableObject does not allow to alter complex property ? RRS feed

All replies

  • hello again,

    I answer to myself and change type of the post.

    I finally move the management of the default values in a controller build with an IRepository interface/patern.

    The IRepository concrete implementation class encapsulate the DbContext, and so manage the integrity on a constraint way. No more default in the IValidatableObject.

    The controller manage the defaults and the business.

    It sounds like well... but still disturbing me somewhere.

    If any comment, feel welcome. Of course we stay in an EF context, not a general MVC discussion.


    thierry
    Wednesday, August 24, 2011 11:28 AM
  • hello,

    i continue my self conversation.

    In this case I have the problem of the children entities that also have default values that must be set.

    It woul really be good if we should manage defaults at the entity level, not at the controller level.

    thank you


    thierry
    Wednesday, August 24, 2011 4:48 PM