ASP.NET vNext is host agnostic, what does it deeply mean?

Question

According to ASP.NET vNext tutorial:vNext is host agnostic . You can host your app in IIS, or self-host in a custom process

Could anyone help me to unde

Answer 1

Keeping in mind that vNext is still a very brightly coloured fast moving object, as things stand currently, it's kind of "half" host agnostic.

The middleware spec that it defines and applies does allow for a very generic interface for arranging programs. So the way you develop is the same. But vNext apps are themselves servers and in a strange way, are currently required to include glue libraries for the type of server you're using.

You can observe this by seeing that you must supply what type of server you want to use inside your project.json file. If vNext projects were truly agnostic, you would select a server at a systems level and point to, mount or launch your app from the chosen server.

It's somewhat complicated because of the lifecycles involved, after you're done here, I encourage you to head over to this github issue on the vNext project where I'm trying to advocate a truly decoupled design.