Home/ Questions/Q 92297
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T23:09:53+00:00

I’ve recently asked a question on StackoverFlow about the MVC: Can the MVC Design

  • 0

I’ve recently asked a question on StackoverFlow about the MVC: Can the MVC Design Pattern / Architectural pattern be used in Desktop Application Development?

Based on the answer provided I started research on how this would be implemented in a Windows form Application. I came upon the following CodeProject article: http://www.codeproject.com/KB/cs/model_view_controller.aspx

In the comments below the article, certain users argue that (although this is a good article) it is actually the observer pattern. First, but less important, question is does anyone agree or disagree with that and why?

Regarding the second and more important question: I’m trying to build a small task list program in .NET. It will be very tiny and hopefully fast. In general, what would be a better architecture for such a project? The Observer Pattern or the MVC Pattern? Or another pattern?

Thank you

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. (The article is not an example of MVC AFAIK for the simple reason that there is no controller.. it is more close to .net data binding if you ask me.)
    MVC is not the Observer pattern. MVC is concerned with separation of concerns. The Model, the View and the Controller all do one job and trust the others to do theirs. In a way, the Controller ‘directs’ the view and tells it how to react to a change (Pure MVC). The controller also interacts with the model appropriately (whose responsibility is to encapsulate data and enforce constraints/rules). In MVC, the controller is the starting point for all activities – user input is received by the controller first.. However there are variants like MVP, where the user is input is received by the view first and then pushed/synched with the presenter.

    The Observer pattern is where you want to watch another object for a change in state. So you could say .net events follow the observer pattern

    If its really tiny, forget about patterns and just code it up without worrying about the architecture… Follow the heuristics/principles of good design

    If you run into design issues or it starts to get all messy, then bring in the pattern battalions.

    • 0