In this session we cover different aspects of Hyper-V Recovery Manager, an enterprise-scale Disaster Recovery solution to provide a single click failover in case of disaster (e.g., automation of overall DR workflow using with sequencing, manual actions, etc. to provide both application and site level DR). We cover the most frequently asked end-point support from our customers: Azure to help save precious CAPEX. Learn how to enable Azure as a Disaster Recovery point in a secure manner and seamless management of failover, failback type activities using Azure IaaS VM. Network connection—back to datacenter and to the clients—is one of the top challenges in setup of your DR infrastructure and we cover how to simplify networking for disaster recovery setup. The session also covers enhancements to the solution for the private datacenter to the private datacenter scenario.
In a world where a person’s portfolio of devices and peripherals interoperate seamlessly, docking plays an important role by enabling portability and productivity through quickly, seamlessly, and more securely connecting the peripherals a user needs to accomplish a task. This session will provide system and device builders with the guidance to create great hardware that lights up the Windows 10 docking user experience. Topics include: overview of the Windows 10 docking user experience, implementation details for docking technologies: WiGig, Miracast, USB type-C, and guidance for solutions with custom docking connectors. Intended Audience: OEMs, ODMs, IDHs, IHVs, Peripheral Manufacturers, Driver Developers.
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.