Currently Cormo only supports web-api. Not MVC.
I'm not sure whether I'll want to invest too much on MVC anymore, considering that asp.net vNext will merge the two (webapi and mvc) into a more streamlined framework, rather than requiring me to write 2 different implementations on 2 completely different codebases.
So for now, the only feature I'll add to MVC will be just dependency-injection on MVC controllers, but not much beyond it. More effort will be spent on web-api stuff, in the hope that it will be easier to be ported to vnext.
Low priority.
Currently Cormo only supports web-api. Not MVC. I'm not sure whether I'll want to invest too much on MVC anymore, considering that asp.net vNext will merge the two (webapi and mvc) into a more streamlined framework, rather than requiring me to write 2 different implementations on 2 completely different codebases. So for now, the only feature I'll add to MVC will be just dependency-injection on MVC controllers, but not much beyond it. More effort will be spent on web-api stuff, in the hope that it will be easier to be ported to vnext. Low priority.