Move MvcApplication to Microsoft.AspNet.Mvc assembly

[davidfowl]

Move MvcApplication to the Microsoft.AspNet.Mvc assembly so that we can have a fallback for when the service provider isn't composed with MVC services. It'll make the following possible:

using Microsoft.AspNet.Abstractions;
using Microsoft.AspNet.Mvc;
using Microsoft.AspNet.Routing;

namespace MvcSample.Web
{
    public class Startup
    {
        public void Configuration(IBuilder app)
        {
            var routes = new RouteCollection()
            {
                DefaultHandler = new MvcApplication(app.ServiceProvider)
            };

            routes.MapRoute(
                "{controller}/{action}",
                new { controller = "Home", action = "Index" });

            routes.MapRoute(
                "{controller}",
                new { controller = "Home" });

            app.UseRouter(routes);
        }
    }
}

The code to fallback would look something like this:

public MvcApplication(IServiceProvider services)
{
    _services = services;
    // Look for some marker that indicates if Mvc has be configured 
    if (services.GetService<IActionSelector>() == null)
    {
        _services = MvcServices.GetDefaultServices()
                               .BuildServiceProvider(services);
    }
}

The check itself can change but we just need a way to figure out if the service provider is composed for mvc or not.

[yishaigalatzer]

@davidfowl is this still relevant?

[davidfowl]

Nope