Deep Dive into ASP.NET 5

Download this episode

Download Video

Download captions

Download Captions


This talk will take you deep into the internals of the all-new ASP.NET 5 framework. This new, fully open source web framework sits on top of the new composable cross-platform .NET Runtime - the Core CLR. Damian Edwards and Scott Hanselman will show you how ASP.NET 5 enables more choice than ever before. ASP.NET 5 gives you more choices for platforms, tools, libraries, runtimes, and more.
For more information, check out these courses on Microsoft Virtual Academy:





Session Type:





Hall 1B



Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image

      Fantastic presentation, thank you

    • User profile image

      great, Great, GREAT talk!

      Have been following ASP.NET development (standups etc) for a while now but still got to learn a lot of new things!

    • User profile image

      Fantastic presentation!!

    • User profile image

       Learned a lot!

    • User profile image

      57:30'' : it's 'smitten'. I won't even bother verifying, this is classic stuff we learn to get a foreign language certificate for English... ;)

    • User profile image
      Suresh Burdak

      I've downloaded Visual Studio 2015 and created an empty project. What I cannot work out is how do you create a new view from within IActionResult, in VS2013 you could right click and create it. But now there appears to be no option for this.

      The only way I can do it, is to create the view manually.

      Am I missing something simple

    • User profile image

      one word: Terrific :)

      Great job guys! really great job!

    • User profile image
      Elliot Wood

      Mind blown... great job MS!

    • User profile image

      Attaching source code in global.json seems very elegant, but there are more things that happens after you do that. Namely dependent project is added as a solution dependence in "Solution Items" section of *.sln file (with path to the source location). Now if you keep your sln in VCS you don't want to check this in, because location of your local copy of source of dependent project (which was initially added as nuget package) is user specific. So why do we have this data added to sln file?

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.