Hi,
I been building my first ASP.NET MVC application and so far am getting to grips quite well with it I think. Some of the concepts are still fuzzy (routing) but I have an idea.
One of the things we do with our WebForms apps is to route navigation through an Application Controller [Fowler] to handle our page navigation based on the current application state.
Although it seems very easy to do navigation with the MVC controllers (and I've adopted the pattern of one controller to several related views.... almost like a use-case controller, which is working well so far) I was wondering if the Application Controller pattern is an overkill in this situation. I have a few scenarios where in the controller I am applying logic (e.g. if x show this view otherwise redirect to y) ... which seems a controller type thing to do... but I still have a gut feeling that it would be better to strip this out to an Application Controller for testing an seperation of concern.
What do you think?