ASP.NET 5 is a lean and composable framework for building web and cloud applications. It's fully open-source and available in Github. Composable meaning components that are "self-contained" (modular) that can be deployed independently and "stateless" that treats each request as an independent transaction, unrelated to any previous request. This is based on the .NET Execution Environment (DNX) that supports running cross-platform on Windows, Mac and Linux.

When configuring DNX, you need to pick the .NET flavor also (.NET Framework / .NET Core / Mono) and DNX and .NET Core is available for the greatest number of scenarios. The choice can be made based on the requirements on compatibility. Let's look at the pros and cons of each one.

.NET Framework

Pros:

Cons:

.NET Core

Pros:

Cons:

Mono

Pros:

Cons:

ASP.NET 5 provides the following many improvements over its predecessors:

One important thing to note is Single Page Applications. A modern web application uses a combination of server-side and client-side behavior. ASP.NET has evolved over time to support more client-side behavior and with version 5 it includes support for Single Page Applications (SPAs) that virtually shift all the logic of the application to the client side and uses the server only for fetching and storing data. Your application approach to where its behavior resides will depend on a variety of factors.