C# Best Practice for Seperating Windows Form

[neffc]

Can anyone point me to an example that seperates your Windows Form and it's events away from the class that actually carries out your Application logic?

[leppie]

CN78 wrote: Can anyone point me to an example that seperates your Windows Form and it's events away from the class that actually carries out your Application logic? Yes, create a new C# file, without any controls in it :) top secret xacc-ide 0.0.1

[Colin Angus Mackay]

Model-View-Controller Pattern[^] This article describes the MVC pattern in relation to web pages, but many of the ideas also apply to Windows Forms. From the above link: The Model-View-Controller (MVC) pattern separates the modeling of the domain, the presentation, and the actions based on user input into three separate classes [Burbeck92]: Model. The model manages the behavior and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller). View. The view manages the display of information. Controller. The controller interprets the mouse and keyboard inputs from the user, informing the model and/or the view to change as appropriate. Does this help?

---

"You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar The Second EuroCPian Event will be in Brussels on the 4th of September Can't manage to P/Invoke that Win32 API in .NET? Why not do interop the wiki way!