Interaction Service vs Interaction Request Objects

Question

I'd like to know when using Prism, Interaction Request Objects is preferable to using Interaction Service pattern. As for me, Interaction Service should be used in simple cases, i.e. when you have a standard message popup, and only the text content is going to be changed. On the other hand, Interaction Request Objects is more suitable when the UI is more complicated. But Interaction Service is much easier to implement and requires less code. What do you think?

Answer 1

The huge drawback of using an interaction service to display a message box is the parent window - or rather the lack of one.

What window should you provide as the parent of the message box, from the view model or service implementation? If you choose Application.Mainwindow, you're making a huge assumption about the overall application layout.

The only entity in the process that knows how to display the interaction is the view. Whether that be using a message box, or in-page overlay.

There are few valid arguments in favour if using an interaction service. The one often used is that it's easier. This may be true, but is also true of many other things that shouldn't be done, e.g. code behind, etc.