views:

131

answers:

2

I have a .NET MVC winform app. I've created an AppDelegate class that handles application startup and shutdown...for now (it might do more later). Winform apps have a Program.cs file that does some app initialization, starts the message pump and creates the first form. In my app, the first form is AppDelegate, which isn't really a form but is forced that way by Application.Run(). AppDelegate does any further app initialization and starts the first Controller, which then initializes any child controllers (these then create their views).

I don't consider events occuring in Program.cs and AppDelegate as part of the MVC. Conceptually, what would these be called?

A: 

you can call Application.Run without a form to start a message loop, and do whatever you want afterwards like call your AppDelegate. It doesn't have to pretend to be something it's not then.

Sekhat
A: 

Awesome. Thanks. Any idea on the other questions?

4thSpace
Application Initialization? :P Even using MVC in web apps, execution doesn't begin at the Action in the controller being called, theres a bunch of initialization stuff that occurs (and lots of it) well before any controllers or models get called. So you could say your initial code is literally just initialization code to get your app into a state where you can run all your MVC patterned stuff nicely.
Sekhat