Any recommendation for a good enough Winforms GUI design?

Question

I am developing a mid-size application with VB2008. To better test my application I am following a MVP/Supervising Controller approach.

My question is: What are your recommendations to separate responsibilites? So far I've come up with a winform with an instance of a controller and with an instance of my class. The controls are updated via DataBinding

The problem is that I'm just not sure where to write the responsibilites (let's say Validation, Report creation, Queries and so on) Inside my class? in a separate class?

Is there any small example of a clean Winform class design that you could point me?

Answer 1

Martin Fowler is a good source of information on all things design patterns including MVC. Fowler discusses Passive View and separation of responsibilities is demonstrated also

http://martinfowler.com/eaaDev/ModelViewPresenter.html

Answer 2

I would suggest you spend time reading Jeremy Millers 'Build your own CAB' series of posts to get a feel for what you might like/need to implement as your application becomes more complex.