Today, people want to work anywhere on any device. How do you enable this, yet retain control and meet compliance requirements in both on-premises and cloud environments? Join us to learn more on the Microsoft hybrid identity story, Active Directory Federation Services (AD FS) in Windows Server 2012 R2 improvements and Microsoft Azure Active Directory.
• See the math and visual science behind how Windows abstracts physical display density and viewing distance • Why this means you can work in effective pixel space across all devices • How Windows makes full use of the physical pixels for you • What has changed for Windows 10 and why • When you have to know about physical pixels and why: bitmap assets and layout grids • How assets are picked through MRT and how to use MRT to manage assets and asset packs • Guidance: best practices on which scale factors to support: tradeoffs between quality and footprint • How to port assets from other platforms to Windows apps • Why scaling and layout grid go hand-in-hand, and the benefits of sticking to the layout grid • When you have to know about physical pixels and why: some advanced application requirements and techniques • API support you need to write an app that knows about physical pixels Speaker: Steve Wright
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.