Hi everyone,

I have been mixing Umbraco with standard MVC for the last couple of problems and it is working perfectly. For me this is the ultimate solution for Umbraco letting you build a proper MVC website mixing standard controllers (i.e. just extend Controller - have nothing to do with Umbraco) and Umbraco RenderMvcControllers (for rendering Umbraco routes) where appropriate. I'm loving it.

The only thing I had to do to get this to work was ensure I didn't have any defaults set up for the default MVC route

{controller}/{action}/{id}

If I had default set up the Umbraco RenderMvcControllers never got called and I got a blank page when browsing an Umbraco route.

I actually use AttributeRouting so this is kind of legacy for me anyway.

Is this all working as designed or am I just currently exploiting some random issue with Umbraco. I ask because I don't want to find in a future release I cannot use native controllers any more. I also now wonder what the point in SurfaceControllers are in this scenario?

cheers,
Robert