Apps should be tested before submission. Every app is unique, so a unique test plan should be created to test the components of each app. When creating the test plan, a few factors should be taken into account: app modules; how those modules interact within the app and in which order they are initialized; and which modules are required for the app to run. Based on this info, the modules should be tested. In this session, Mickey talks about how, through testing, you can ensure the highest quality for your app.
Even though you're watching this on-demand, Mickey wants to help. Post your questions, comments, etc below or tweet it, mentioning @cdndevs.
In 2013 the Lync 2013 Managed API for the Lync 2013 client has added a series of new capabilities, especially for building Kiosk style applications, such as video and application sharing. This session will give an overview of these capabilities.
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.