Visual Studio 2013 has been a small jump in version number from 2012, but don't be fooled – from your first time using it you discover it is the little things that make a big impact in your day-to-day development friction. In this session, Colin Bowern highlights the little changes from getting started to optimizing your app that make this a worthy upgrade for your tool chain, no matter the type of application you build.
ASP.NET vNext is a lean and composable framework for building web and cloud applications. ASP.NET vNext is fully open source and available on GitHub. ASP.NET vNext is currently in preview, and in this talk Fowler and Edwards will put it all into Context. vNext apps can use a cloud-optimized subset of the .NET framework. This subset of the framework is about 11 megabytes in size compared to 200 megabytes for the full framework, and is composed of a collection of NuGet packages. What does that mean for compatibility? When would you choose vNext and when would you not? You don't have to use Visual Studio to develop ASP.NET vNext applications. You can develop and run vNext on platforms that Visual Studio doesn't run on. But Visual Studio provides the best development experience, and we'll cover ASP.NET vNext both inside and outside the IDE.