I can tell from my own experience that having MVC apps running side-by-side with C1 works fine. On this website for instance http://oqaasileriffik.gl/, we have a whole Administration Application created in MVC which runs in a Admin area (http://oqaasileriffik.gl/Admin/KlWord).
The route registration simply looks like this
The route registration simply looks like this
AreaRegistration.RegisterAllAreas();
routes.IgnoreRoute("{resource}.axd/{*pathInfo}");
routes.IgnoreRoute("{*allaspx}", new { allaspx = @".*\.aspx(/.*)?" });
routes.IgnoreRoute("{*favicon}", new { favicon = @"(.*/)?favicon.ico(/.*)?" });
routes.MapRoute("Default", "{controller}/{action}/{id}", new { controller = "KlWord", action = "Index", id = UrlParameter.Optional }, new [] { "Oqaasileriffik.Web.Controllers" });
And while the C1 MVC Player works fine for simple controllers and routes, there are issues when hosting whole complex application through it.