What I really would like to do is redefine the conventions to do the following:
For controllers and their respective actions:
If a URL request is given and there is no controller with the action provided, perform some of the "default" functions that I will set for myself in the application. I would have thought that this could be achieved using Func <>, but I'm not sure where to turn it on.
For views:
If the controller action requests a view, and there is no view that matches the request that requests the controller action, return that view by default.
Is this something possible, and if so, where should I delve into to find out more about how to do this? Or is it really a simple thing?
EDIT
Here is an example of what I'm trying to achieve.
I have a very simplified view, something similar to this:
<%@ Page Title="" Language="C#" MasterPageFile="~/Views/Shared/Site.Master"
Inherits="System.Web.Mvc.ViewPage<dynamic>" %>
<asp:Content ID="Content1" ContentPlaceHolderID="TitleContent" runat="server">
<%: Html.LabelForModel() %>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="MainContent" runat="server">
<%: Html.EditorForModel() %>
</asp:Content>
So, let's say I have a Customer class, and the controller action does something with the Customer object, and then does
return View(someCustomer);
The problem here is that I did not define any kind for processing the Client. In this case, I want my view mechanism (or something not to respond), saying: "Ok, there is no view that processes Clients directly, instead I use the default view."