Whether you call them "Metro apps," "Windows 8 Design-Style apps," "RT apps," or "modern apps," the new class of applications for Windows 8 and later tablets are not only here to stay, they also offer some interesting advantages and challenges for IT pros. Much has been written about modern apps, but 99% of that was written with developers in mind. That makes a certain amount of sense, as no one is going to ask us IT pros to support software that hasn't yet been written, but given that the Windows Store added its 100,000th modern app back in July of 2013, it's reasonable to assert that the time has come for IT pros to know more about the members of the six-figure army. How are they structured? ARE they more secure? Where are they stored? What options do you have to deploy them? What about "sideloading," the method to roll out home-grown line-of-business apps? Join us for an informative, entertaining, and real-world look at the latest crop of Windows apps!
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.