Home/ Questions/Q 3454418
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T09:29:28+00:00

A common MVVM/WPF approach is to data-bind the UI’s controls directly to the underlying

  • 0

A common MVVM/WPF approach is to data-bind the UI’s controls directly to the underlying model object. The model object may contain its own validation logic (perhaps exposed via IDataErrorInfo) or may be validated by a helper class checks a model object instance for errors. In either case, at times the model have invalid data in it and so be in an invalid state.

However, in the DDD world, the model is never to be in an invalid state. How do you suggest performing validation when using WPF and DDD?

Thanks,
Ben

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m tending to think that a facade or similar layer should be used as the MVVM “model.” This facade can be in an invalid state (unlike the DDD model). For validation, it can either contain its own logic or a tool like FluentValidation can be used. Once it is in a valid state, its “do action” function can be called. This will pass the data in the facade to the underlying DDD model. With this approach, at no point does the DDD model encounter invalid data.

    With this approach, the facade and its validation logic could be used by multiple view/view model pairs, eliminating the validation logic duplication present when each view model does its own validation.

    • 0