Monumental shifts are hitting the workplace, necessitating changes in how and with whom we communicate and collaborate. For the first time in history, four different generations are working side-by-side in the workplace. Each generation of end users has distinct attitudes, behaviors, expectations, habits, and motivations. Add to that the increasing need for agile communication between every corner of your organization, from the retail store, across the shop floor, to the corporate office and beyond. Office 365 enables IT to unify end users across generations and departments under one technology. The communication and collaboration capabilities in Office 365 help IT meet the varied needs of these end users. In this session, come learn how IT can make the most of these capabilities in Office 365 to support the needs of every end user to help them be more productive at work.
Optimization is very hard topic which requires deep understanding of how underline system works. While every app is unique in its implementation, there are common areas that might improve app performance and memory usage in general. This especially true when apps were updated from previous versions on Windows. In this session, Mickey MacDonald talks about these common areas, how to optimize, and how to plan for low memory and hardware constraints.
Even though you're watching this on-demand, Mickey wants to help. Post your questions, comments, etc below or tweet it, mentioning @cdndevs.
Вопросы эффективного управления тестированием - управление большими тестовыми моделями, анализ структуры дефектов, планирование, учет и оптимизация ресурсов. Лучшие практики, а также опыт использования и настройки Microsoft Test Manager.
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.