take a look at how MS MVC and MonoRail manage webpages. this is a true MVC implementation.
controlers direct the flow of the presentation. A user resquests a controler (usually determined by the URL). the controler is initiated and accesses the model.
any output from the model is placed in a container which is passed to a view. the view renders the contents of the container.
in this scenario the view has no knowledge of the model's purpose, strucuture or interaction. it only knows to take item(s) in the container and display them using HTML.
the controler doesn't know what the output looks like, only what information is required of the view and what view to render.
the model doesn't know how it will be presented. it is only responsible for managing the interactions between domain objects.
an ASP.Net MVC is a drastic depature from webforms. there is no sense of postback, view state serves no purpose and the web page is not event driven.
infact, MonoRail does not use webforms at all. it uses a templating engine (Brail I think) there is no code behind, postbacks, view state or server side controls. pure html and the contents of the container. Looks alot like php/asp 3.0.
MS MVC allows you to inject any type of view engine you want. the default is WebForms. this gives you the ease of data binding and serverside controls. but comes with the viewstate and autogenerated client id tax.
it would also be tempting to mix web form events with the MVC which defeats the purpose of MVC.
Specialty Bakers, Inc.