Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Apr 08, 2009 12:00 AM by Naom
Apr 03, 2009 02:23 AM|LINK
Is MVC a UI layer pattern or an architectural pattern to be applied across all layers in a tiered application
Apr 03, 2009 07:10 AM|LINK
If you're working in a n-tiered or n-layered environment (as I do) then the MVC project will be your UI layer.
Apr 03, 2009 10:23 AM|LINK
Hello rgmailtest, welcome to the ASP.NET community forums.
MVC is very misunderstood. I strongly urge you to read
Martin Fowler (http://martinfowler.com/eaaDev/uiArchs.html) ~~ his "GUI Architectures" essay.
Also, you'll find many useful references at
You asked whether "MVC a UI layer pattern or an architectural pattern to be applied across all layers in a tiered application".
MVC in general is neither. The View of MVC concerns itself with
The Model of MVC concerns itself with being a
black box of black boxes
wherein the soul of your application lives. The controller (small "c" deliberate)
of MVC is the servant of the Model.
MVC should really be called McV.
The work of the controller is to direct user input that comes from the
to the Model and to be a messenger for the Model in telling the
what the Model wants displayed to the end user.
the Model is the brains of the
the controller is the messenger of
the application, and
the View is the speaker for
In a non-trivial MVC application, the
Model will do the most real work,
then the View, and last the controller. Each has an important role to fulfil.
MVC is far to big conceptually to be thought of a a pattern.
MVC in general is a conceptual paradigm that can be thought
of as an umbrella for many patterns. The MVC umbrella covers
all tiers of an application.
In particular, ASP.NET MVC is a paradigm that allows ASP.NET
application architects and developers to implement MVC in the ASP.NET world.
Apr 08, 2009 12:00 AM|LINK
Thanks, sounds like something I need to learn. I was skipping it so far...