Your carefully written and tested program has been deployed to your customer and it's not working properly: It crashes, it hangs, it doesn't start properly, it's using much more memory than it should be... It's basically not working properly and you have no idea why. To make matters worse, you can't reproduce it in your development or testing environment. But not only that, your customer is very restrictive about installing extra software on his production machines. So you can't even install an update of your own application to help you pinpoint the problem. So, what do you do?
This is what this session is about. We're going to show you some tips and tools that can help you in situations just like that. We’re going to be focusing mostly on managed code (.NET 2, 3.x and 4), but some of the tools help for unmanaged code as well.
 
Bio:
Michael Vanhoutte is the CTO of Adam Software and is the lead developer of the engine of the company’s Digital Asset Management framework. This engine is being used worldwide by companies like RAPP, Lego, Eidos, Microsoft and many others. He has over 15 years of experience working with Microsoft technologies. He’s passionate about software development and about building a team that develops software that is recognized as the best of the world. Michael also blogs about ADAM at http://blogs.adamsoftware.net.