回答2:

I actually think Wikipedia's page on MVC has a very good overview of the Model View Controller architecture.

You can do MVC with Windows Forms and C#, but it is more difficult than with other platforms. MVC is all about separation of concerns - and should be usable with any platform. However, certain platforms make this much easier than others.

The "trick" to getting this to work well in a Windows Forms application is making sure to have a clear separation of concerns in how you design your forms. Try to keep some separation between the event handling (controller), the form design and layout (view), and the business logic and design (model). The basic design of windows forms doesn't explicitly force or guide you to having this separation, so it will just be up to you to keep those things separate.

The trickiest one in Windows forms is keeping the view and controller from getting too interdependent. The WinForm designer naturally puts all of the event handling into the same class as the form, so it's easy to get the two things tied together. You'll have to keep that separation in place yourself, if you want to follow the class MVC architectural patterns.

回答3:

How about this SO post. This has a good overview of that they are.

回答4:

Start by reading Martin Fowler's comparative article on different GUI Architectures. It covers MVC (as MVP used to be called) and a lot of other useful information that should help to frame the concepts for you.