I've loved the work you've done but It needs some extensibility on the view it renders. I see it supports only asp.net built in page extensions like .aspx or .ascx for processing views. If it supports registered handlers within the application or it uses view classes instead of .aspx files, it would be more extensible.

Now, the following code:

RenderView("About");

executes "About.aspx" some where and if I register an '.abc' extension within my custom handler, it does not recognize it.

Mohammad

You can use the controller's ViewFactory property to provide your own View Engine implementation. If you are using an IControllerFactory you can set that automatically in all your controllers. Using an IoC container to instantiate your controllers will make this even smoother.

tajari:

If it supports registered handlers within the application or it uses view classes instead of .aspx files, it would be more extensible.

You don't need handlers with mvc.  Your controller has total control over what view gets rendered, and routes allow you to map anything to a particular controller.

If a request comes in /blog/Mvc-Needs-No-Handlers you can render regular html when it comes in /blog/Mvc-Needs-No-Handlers.xml you can output xml.  You can also checkout this post for outputting an image.

I think this is what you are asking?

Hi Tajari, 

tajari:

if I register an '.abc' extension within my custom handler, it does not recognize it

I believe you should also register ISAPI filter in the IIS to support other extensions.

Have a look here.

Regards,
Dmitriy.