Is MVC/MVP with Winforms an anti-pattern?

Question

I have seen some developers attempting to shoehorn the MVC or MVP patterns into Winforms applications, presumably on the premise that, if it's good for WPF and ASP.NET, then it must be good for Winforms.

Is this a good idea, or is it lipstick on a pig? Why or why not?

Answer 1

Most certainly not. I prefer MVP but either are much better than embedding logic in winforms.

Both for testability and best practice.

Answer 2

Once, I would have say : it is NOT a good idea, because the mix gives a unmaintainable code ...
But, have a look at this framework...

Answer 3

One of our most recent development efforts produced a MVP windows forms application. The benefit we saw from using this pattern was that all of the subsequent changes that we made have been quick and easy because we either already had the hooks into the functionality that we needed or we could very quickly create them by following the patterns already implemented in the application.

Answer 4

You may find the answers to Implementing MVC with Windows Forms helpful as they talk about the different options when implementing MVC and MVP