In this session we'll look at how to use Visual Studio 2015 to continuously improve the performance of your applications during normal development. You'll learn how to use the new capability of running diagnostic tools with the debugger and how to use the tools without the debugger to diagnose a broad range of performance issues.
Il PaaS è l'acceleratore di qualsiasi business, sia quelli in crescita rapida, che quelli maturi. Per i primi, i WebSites rappresentano la via veloce per ottenere un risultato talvolta complesso; per i secondi, essi rappresentano un modo per ridurre la governance e i relativi costi, pur mantenendo in primo piano i requisiti di scalabilità e affidabilità. Vedremo quindi come WAWS è l'acceleratore del nostro posizionamento sul web, utilizzando un importante caso di studio di una emergente realtà italiana.
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.