>
I'm having a hard time understanding what these pieces represent. I get the Model. That appears to be the data layer. But the View
>and Controller portions are throwing me. >
>These can be difficult until you really "get" the context in which they're used.
From what I can see from this article
http://msdn.microsoft.com/en-us/magazine/cc188690.aspx, the Model represents the data layer, the View represents the UI, and the Controller is/are events?
The Figure 1 paragraph says:
" Figure 1 shows the main layers that make up the sample application. Notice that there are separate packages for UI and presentation. You might have expected them to be the same, but actually the UI layer of a project should consist only of the various UI elements— forms and controls. In a Web Forms project this is typically a collection of ASP.NET Web Forms, user controls, and server controls. In Windows Forms, it is a collection of Windows Forms, user controls, and third-party libraries. This extra layer is what keeps the display and the logic separate. In the presentation layer you have the objects that actually implement the behavior for the UI—things like validation display, collection input from the UI, and so forth."
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people