The WPF Team at Microsoft has posted the 0.1 edition of the WPF Application Quality Guide. There's still a lot missing, but it does have good tips on how to set up your WPF application for automated testing.

Here's a list of tools they recommend for performance profiling:

Using Performance Profiling Tools for WPF.

Event Trace. Use this tool for analyzing events and generating event log files.

Perforator. Use this tool for analyzing rendering behavior.

ETW Trace Viewer. Use this tool to record, display, and browse Event Tracing for Windows (ETW) log files in a WPF user-interface format.

Visual Profiler. Use this tool for profiling the use of WPF services, such as layout and event handling, by elements in the visual tree.

Working Set Analyzer. Use this tool for analyzing the working set characteristics of your application.

I also feel the need to plug the best visualizer out there, Mole!

Earlier I wrote about how I felt pwned during my first session at the South Florida Code Camp.

Luckily, things turned around during my second session. I was unable to turn it in a discussion as I had planned. The room was still set up to serve presentations, and some of the people I would have liked to have in the discussion (like Scott Dorman) were busy with their own sessions. However, everything went smoothly during my second presentation. I had great crowd interaction, and I received good applause at the end. It was definitely a contrast to the earlier session.

I was unable to make it to the after party. My wife doesn't turn 25 until March, so I had to drive her back to the hotel to freshen up. Car rentals don't cover under-25s unless you want to spend an arm and a leg. We ended up on the wrong side of Miami in the process. You know, when you head north on a highway, you expect to go south to return from whence you came. This proved untrue with the Florida Turnpike, which apparently has three directions. We ended up eating at a great Argentinian restaurant though, so not all was lost.

I had a great time at this code camp, and I learned new lessons on presenting. I also met some great people like Dave Noderer, Joe Healy, and David Silverlight. Next time there is a Code Camp in Florida, I hope to make it down. I even have a great new presentation planned that should be ready by April (with an accompanying project I will release to the community).

I just finished my session on Design Principles in the South Florida Code Camp. I feel kind of pwned  by what happened at the beginning. I should have expected it. After all, there are over 600 people here, and I warned everyone at the beginning that it was meant to be an introductory class (hence the 100 level). The presentation still has good nuggets even if you're an experienced developer.

My room was packed. About 5 minutes into it, 20-30 people walked out. Having all those people get up, walk by me, and opening the door distracted me. I lost my focus, and it took a while to get my bearings. I need to keep in mind that this can happen and not let it get to me. I can't believe I actually faltered.

I realize I didn't write about my experience in Philadelphia. I had an incident there as well. At the beginning, the projector messed up. I spent a few minutes trying to get everything working but eventually realized I would lose the audience if I didn't move on. I ended losing my local screen, and had to move the desk around and look at the projection This prevented me from using my slide deck. Luckily, I knew my material well enough to talk while doing demonstrations (though I strained my neck). It ended up being successful. albeit unstructured.

After I did my presentation here in Miami, I spoke to Joe Healy about it. He mentioned something about my session at the end of the day. I didn't even realize I am doing another one! This time it's in the Birds of a Feather and Panel Discussion room, so I'm going to make it a discussion rather than a presentation.

I'm leaving soon to make the third stop on my 2008 presentation tour! Okay, it's not like I'm doing a world tour or something, but I do plan on presenting at 20 different in-person events this year. The travel expenses are coming out of my own pocket, so I expect to keep it along the eastern seaboard (US).

I hope to see everyone tomorrow at the South Florida Code Camp. I'm doing the Design Principles session in the Architecture room. Unfortunately, I'll be arriving too late in Miami to make it to the speaker reception tonight. I didn't realize they were doing that or I would have tried to catch an earlier flight.

Larry Port will be doing a Continuous Integration presentation (I submitted one, but I guess he got in first). I plan on seeing his take on everything in case it inspires some ideas for my own CI presentation. I'm kind of curious about his focus on NAnt though. I prefer MSBuild. Here's one reason why: If I want to upgrade my project to .NET 3.5, MSBuild already works because MSBuild is part of the .NET Framework. NAnt's 3.5 support is still in beta. Here's another reason: you still have to call MSBuild from NAnt to build the project. Oh, you can call devenv, but then you've installed unnecessary software on the build server (a big no-no). Perhaps NAnt buys you something that MSBuild doesn't, but I won't know until I ask.