Have you ever been looking at code and fantasized about pummeling the programmer who wrote it? Has that programmer ever been you? Do you have functions and classes in your solution that aren’t used at all? Has making modifications to your existing apps ever felt a little like playing Jenga, because you’re unsure if this change is going to cause the whole thing to collapse?

Test Driven Development is both a philosophy and a programming technique that helps to ensure you never have to answer yes to any of those questions if done properly. We are going to look at how TDD will help you to write cleaner, more succinct code that has full testing coverage. I will show you how TDD done properly can result in better design, and give you the confidence to aggressively refactor your code without fear of breaking existing functionality.

The first part of the presentation will be an overview of TDD, some design principles and patterns involved in effective testing, and the major benefits from using TDD on a project. The second part of the presentation will be a live demo where I will build a small application (with audience participation) using TDD in order to demonstrate the various techniques discussed in the first part of the presentation. We will wrap up the presentation with time for questions and practical steps to implementing TDD in your environment.

PowerShell, Microsoft’s long awaited interactive command line scripting language, has finally arrived. It features an object-based command shell integrated over the .NET framework. Borrowing from the Unix model, PowerShell contains a large number of small operations that, when combined in interesting ways, can quickly and easily tackle complex tasks. But unlike Unix, which uses byte streams to pipe data between commands, PowerShell uses object to communicate between its “commandlets” - lending new possibilities to this proven method. PowerShell also includes a rich dynamically typed scripting language, built-in data structures, regular expressions, and it is easily integrated with new applications.

But first - why would we need a tool like PowerShell? When working on a Windows platform, system admins and developers have never had a native scripting language with much power or grace. The Cmd shell can be useful for simple batch operations - but it is ultimately crippled by lack of visibility into the depths of the OS. VBScript somewhat addressed this need for a complex scripting language - it now has extensions giving access to XML, ADO data structures and IIS. These capabilities have been cobbled over of the language over course of 10 years - they can often be cumbersome and non-consistent. On top of this, some administrative tasks can only be performed inside a GUI. PowerShell was written with the intent to solve these problems.

The development team behind PowerShell have coined the term “Admin Development Model” to describe their design directive. In this model development occurs in three phases. The first could be thought of as “hair on fire” mode - you’re needing to get something done quickly and who cares what short-cuts you need to take. The next mode, presumably after the flames subside, you’ve got some time to look over the damage and develop some robust scripts based around the quick fixes. Finally, it might be that the scripts serve a business need - you could encapsulate the functionality in a nice GUI that anyone in your organization could use.

In this presentation we will be exploring PowerShell in a hands-on overview and interactive demo. We will cover the interactive shell, the scripting concepts, and GUI integration. Whether you’re a systems admin, developer, script wizard, troubleshooter, or average Windows desktop user, PowerShell can be a powerful tool in your technology arsenal.

Service-oriented architecture (SOA) has emerged and gradually matured as a means by which to make software assets available and reusable within and across corporate and geographic boundaries. What, exactly, is an SOA, though? What is an enterprise service bus, or ESB? What is a message bus? How are these concepts and technologies related, and how and when can they be used effectively?