Mark Seemann, Creator of AutoFixture; author of Dependency Injection in .NET

Mark Seemann

Biography: Mark Seemann

Mark Seemann is the inventor of AutoFixture and the author of "Dependency Injection in .NET". He is a professional software developer and architect living in Copenhagen, Denmark, and currently the Windows Azure Technical Lead for Commentor, a Danish consulting company. He enjoys reading, drawing, playing the guitar, good wine, and gourmet food

Presentation: "Aspect-Oriented Programming with Dependency Injection"

Track: The New and Awesome in .NET / Time: Wednesday 10:35 - 11:35 / Location: Room 204/205

Cross-Cutting Concerns such as logging, auditing and security often present a difficult challenge because they must be applied to diverse components across an application. This can be difficult to reconcile with principles such as the Single Responsibility Principle and DRY (Don't Repeat Yourself).

One common solution to this challenge is Aspect-Oriented Programming (AOP), but another alternative is to leverage Dependency Injection (DI) to implement Cross-Cutting Concerns in a loosely coupled fashion. This session shows how to do this by progressing from simple use of DI and known design patterns to use of dynamic proxies emitted by DI Containers.

Presentation: "C# (and AutoFixture) Programming with Mark Seemann"

Track: Programming with the Stars / Time: Thursday 14:05 - 15:05 / Location: Room 204/205

Pair up with Mark, as he dives into programming using C# and the cool AutoFixture tool. Or just lean back and watch the programming unfold on the stage.

Presentation: "Azure without SQL"

Track: Cloud and NoSQL / Time: Thursday 16:50 - 17:50 / Location: Room 202/203

Just like on-premise web applications, most cloud-based applications are powered by data. In traditional on-premise architectures, a relational database such as SQL Server is normally used to host the data.

While the Azure platform offers SQL Azure to make migration easier, it also offers a set of highly scalable storage services that take a different approach to data storage: Tables, Blobs and Queues. They pose a new set of challenges to application designers since they are offer no transactional or relational consistency. In this session we will take a look at some practical application design considerations for working with these storage technologies.