Where I work, we have a project, written in .NET3.5 as a webforms project. It is tiered; presentation layer, logic layer, and data later.
We have these weekly 'tech sessions' at work. I gave a presentation about MVC.
My tech lead decided to cut in, and tell me that the project above (tiered, webforms) is the same as MVC. He went on to describe the following:
Long story short - we got into an unsettled debate over whether the project described above (tiered webforms) constitutes MVC or not.
Can someone provide and answer to this debate?
Thanks
no. mvc is used mostly for strong separation of concern. the controller and view are not tied together and have no knowledge of the other besides the passing of a model (or not). a single controller can be used to render many views, where as the aspx code behind is strongly tied to a single aspx page, as they are all part of the same partial class. the model is less different, other than to say in most mvc applications the models are not the actual domain data types, but rather some composite that can be used to render the view.
the other thing that is different with mvc is the rigid heirarchical folder structure and naming convention. this promotes best practices and, again, separation of concern.
microsoft created the asp.net mvc framework for a reason, and though you may be able to emulate some the feel of mvc in web forms using routing and such, it is not and won't ever be quite the same thing.
also, while this has been slanted toward asp.net mvc, there are obviously many other flaors out there. i'd suggest you check out FubuMVC as well.