This presentation discusses Microsoft Application Virtualization (App-V) infrastructure design and lessons learned from a series of customer deployments. Topics include Management and Reporting Server design, Shared Content placement/replication, Publishing Server placement, load balancing options, Rapid Scale-out solutions, sizing calculations, and data store configuration options. Examples for using Windows PowerShell to automate and bridge product gaps are demonstrated. Use cases discussed include Published Desktops vs. Applications, VDI Density Reduction, and IOPS/Application Footprint Reduction.
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.