Why use the full .NET Framework with ASP.NET Core?

Question

With ASP.NET Core 1.0 release one can run on either .NET Core or the full .NET Framework per the documentation here. I\'m trying to understand the latter option of

Answer 1

However, if I wanted to use the full .NET Framework, why not just use ASP.NET 4.6?

If I use ASP.NET 4.6 instead of ASP.NET Core 1, then I won't be able to use ASP.NET Core MVC. None of the features on that documentation page would be made available to me! I would have to build an MVC5 application. Boooo!

I'm trying to understand the latter option of why one would select ASP.NET Core + the full .NET Framework?

I'm assuming that another way to ask this would be: "why would you take the red path when you can take the brown path?"

One argument for doing it this way is deployment. If you've got a bunch of existing Windows servers with IIS on them, you're going to need to install additional software on each of them and set them up to run Core applications. IIS just becomes a reverse proxy for your .NET Core app.

However, if these apps were built on the .Net Framework instead, you wouldn't have to do this. You could still use web deploy (for example) to move them onto the servers. Maybe you've got some other existing IIS configuration settings that you don't want to migrate.

Using ASP.NET Core 1.0 targeting the .Net Framework, you can get the benefit of the new features in ASP.NET Core MVC without having to change your existing infrastructure.