Posts Tagged ‘view’
As I mentioned a couple of days ago, the move to DotNetNuke 5 has brought about a few changes. Some of them are design decisions that are just frustrating, like not being able to see that a module is viewable by the administrators only. Others are bugs, like not being able to press the ENTER key while searching for a user, like we discussed a couple of days ago.
Today I’d like to alert you to a design decision that may cause you some trouble.
Last week I introduced the ASP.NET MVC framework by talking a bit about what the model, view and controller are.
In the comments, John Meyer said,
I respectfully disagree with your claim that the model is you BLL. MVC is a UI layer pattern, and as such all models, views, and controllers are strictly in the UI level.
While historically, MVC has been described in the way I stated–while the ASP.NET MVC guys have also portrayed the Model as BLL or below–I have to agree with John. Here’s why:
Last week the ASP.NET Model View Controller framework was released as Release Candidate 1. That’s my cue to take a look at what we finally have available to us and to start a series explaining how it all works.
What we want to take a look at today is exactly what MVC is and why someone might want to use it instead of the Web Forms we’ve been working with ever since ASP.NET came out.
Now that we’ve laid the foundation of DotNetNuke modules, it is time to start looking at the specific modules. While it would be practically impossible to cover every detail and every API feature of a DotNetNuke component, we do want to look closely enough that you know what you are looking at as you are trying to write your code.