Reputation: 7303

Advice on MVC pattern for WinForms app

I'm writing a Windows version of my Mac app (C# Winforms) and would like some advice on what design pattern to use.

My Mac app uses an MVC pattern with Core Data for storage. This is a simplified diagram of the models and relationships:

model diagram

The desktop app collects logs on a background thread and periodically uploads them to my web app. The database is used to store both the user's account information and logs, and the app has a 3 views to display (and collect) the user's data.

I've done some reading and it seems that MVP is the recommended design pattern for WinForms apps, but I'm not sure how to proceed from here. I think that my app is simple enough to write without using an external framework like MVC# but as I have never made a WinForms app before I am only speculating.

Can someone recommend the best way to go about this?

Upvotes: 2

Answers (4)

Joel Gauvreau

Reputation: 3636

Start to work on it, do some screen mockups, do some design, write some code.

You could start with a few small prototype, try out different design. Don't go too far in your exploration phase so that you don't hesitate to throw it away and start over if you need.

Try to keep your choice open as much as possible, don't paint yourself into a corner, and delay this decision until your really need to choose one way over another.

By then you will probably have a much better Idea of what you need.

Upvotes: 0

ferosekhanj

Reputation: 1074

In my experience for a winforms application (which supports nice databinding) you can use MVC with a supervising controller pattern. Read through this question What are MVP and MVC and what is the difference? & http://codebetter.com/jeremymiller/2007/05/25/build-you-own-cab-part-3-the-supervising-controller-pattern/

Upvotes: 1

aqwert

Reputation: 10789

Patterns are really just guides as to what problem it is trying to solve. Where an MVC would work well for a web app that relies on pages and redirects etc a winform app can benefit from using MVP.

Having said that the two patterns are siblings of a wider UI pattern and even according to Martin Fowler the MVP pattern can be further split. Look at his article to get a good feel for the appropriate pattern. He has broken the MVP to Supervising Controller and Passive View. Even the new MPF MVVM pattern is actually based on the PresentationModel pattern.

I would say look at the patterns and see what fits rather than trying to use a pattern because you used it in another scenario.