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.
SharePoint consultants and developers work in projects, and most SharePoint environments are large. As a best practice, the development and test environments should be as equal as possible to the production environment. In reality, SharePoint development and test environments are not as equal as possible. Based on Microsoft Azure Infrastructure as a Service (IaaS), we have a chance to get the environment as equal as possible and to speed up projects and reduce project cost from planning through final deployment of hardware requirements on production environments. Consultants can act faster, or shall we say "very fast". This session demonstrates how to use the Microsoft Azure Management Portal, Windows PowerShell or Microsoft System Center to manage many environments like SharePoint farms in Azure and to deploy the 1-n farms via script, to manage more than 100 cores and terra bytes of VHDs on-demand. Learn how to scale your SharePoint environment up and down, and switch off all resources to scale based on your needs on-demand. Learn to load test on-demand in SharePoint on Azure, for better quality in your production environment. At the end of the Session, you'll understand the latest thinking on Infrastructure as a Service for SharePoint, and the difference from standard hosting. We also discuss how to design a SharePoint Farm for Azure IaaS for Scale-up/-down, and out and off. Focusing on SharePoint and SQL Server and BI, we demonstrate the mechanism to enroll large environments in minutes and to bring them into a very low-cost state for non-business hours, based on demand. With this thinking, IT environments like SharePoint are designed for high availability. At the end of session you'll see the cloud and Azure from a new perspective, and see that hosting is not all the time 24x7, with high availability.
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.