Home/ Questions/Q 6388173
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T03:14:46+00:00

My question is fairly simple and already asked in the title. Here’s the context:

  • 0

My question is fairly simple and already asked in the title.

Here’s the context: I’ve got a domain with entities and repositories. The result of a query is mapped into DTO and sent to the GUI.

The GUI is implemented with WPF and for the mapping, I need classes that implement INotifyPropertyChanged.

My first idea is to have DTO that implement this interface because I foresee a lot of work to map again my DTO into items that implement INotifyPropertyChanged.

Is it a good practice? Has it pitfalls I haven’t seen? What is the “official” good practice for this situation?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    DTOs are supposed to be very simple, lightweight, data transfer objects. Because of this, I wouldn’t implement anything on them other than their data. Also, I believe if serializing the class to/from a WCF server, the properties need to all be public, so you can’t make things like the Id read-only

    I would create Model classes that implement INotifyPropertyChanged and IDataErrorInfo for property changed notification and validation purposes, and have them accept a DTO in the Constructor. Using something like AutoMapper will make mapping a DTO to a Model pretty simple

    • 0