As an infrastructure and security architect, John Craddock has been involved in enterprise systems since the early days of Windows NT. His passion is for determining how things really work and then designing and deploying the most effective systems. John presented on Active Directory at one of the first Windows 2000 launch conferences in Geneva; of course this was only after delving deep into its inner workings. Now it’s time for Windows Server 2012 Active Directory to be scrutinized. Come to this demo-packed session and discover what Windows Server 2012 Active Directory has to offer. Learn about virtualizing and cloning DCs, GUI improvements for password policies and the recycle bin, new Kerberos features, and more.
Contemporary computer architectures make it possible for slow code to work reasonably well. They also make it difficult to write really fast code that exploits the CPU amenities to their fullest. And the smart money is on fast code—we’re running out of cool things to do with slow code, and the battle will be on doing really interesting and challenging things at the envelope of what the computing fabric endures.
So how to write quick code, quickly? Turns out it’s quite difficult because today’s complex architectures defy simple rules to be applied everywhere. It is not uncommon that innocuous high-level artifacts have a surprisingly high impact on the bottom line of an application’s run time (and power consumed).
This talk is an attempt to set forth a few pieces of tactical advice for writing quick code in C++. Applying these is not guaranteed to produce optimal code, but is likely to put it reasonably within the ballpark.
These tips are based on practical experience but also motivated by the inner workings of modern CPUs.
Visual Studio 2013 and the Windows Azure 2.2 SDK provide a rich set of features for diagnosing and troubleshooting Windows Azure Applications. In this video you'll see how to use this new debugging capability through the entire development lifecycle of a cloud application, from the local developer environment all the way through a deployed site on Windows Azure
Windows Azure Cloud Services is an awesome platform for developers to deliver applications in the cloud without needing to manage virtual machines. However, the abstraction that gives you this simplified deployment and scale, prevents you from attaching a Visual Studio Remote Debugger. Sometimes you need visibility into the execution of your production applications. What if you could replay the real production usage with the exact call sequence and variable values using the Visual Studio Debugger? What if you could collect production metrics that would help you identify performance bottlenecks and slow code? In this session, Eric Boyd will walk you through debugging and monitoring real-world Windows Azure applications. Eric will show you how to collect diagnostics like Event Logs, Perf Counters, IIS Logs, and even file-based logs from running Windows Azure compute instances. Next, Eric will also show you how to debug your production Windows Azure services using IntelliTrace's black box recording capabilities. Lastly, you will learn how to collect CLR-level diagnostics and performance metrics without instrumenting your code using tools like AppDynamics and New Relic. If you feel like Windows Azure Cloud Services are a black box when debugging issues and solving performance problems, you will leave this session feeling like Windows Azure is radically more transparent and easier to debug than the applications in your own data center.