Another code camp under my belt, this time the NH .Net Code Camp…I swore after the last code camp that I would never do 2 presentations in one camp again. This time I did 3. I won’t promise not to do that again, because at the rate I’m going, I’ll end up doing 4.
The first presentation was An Introduction to Silverlight Development. Despite pruning some content from the last time, I still ran a little long, so the presentation still needs some tuning. CONTENT HERE.
The second was my talk on Silverlight Line of Business applications. I made one glaring mistake, but thankfully I was able to recover (and remember to add the OrderBy statement to the Domain Service.) CONTENT HERE.
The final presentation was Windows Phone 7 Development with Silverlight. This was the first run for this demo, and it (not unexpectedly) needs work, plus the fact that it is CTP code and the inherent limitations…I am extremely interested in the upcoming Windows Phone product and the idea that it brings development for the new-generation smartphones to the .Net/Silverlight development crowd. I really hope the teams responsible for orchestrating both the initial release and subsequent updates gets this 110% right. Time will tell, but I am hopeful. CONTENT HERE.
Also during the day I saw Talbott Crowell’s talk on F# and Silverlight, as well as John Bowen’s talk on “Thinking in XAML.” There was a great little insightful moment during John’s presentation where he put together a really good description of the relationship between Controls, Templates, and Styles. I’ve heard and red various descriptions of this relationship, but for some reason this one resonated. To paraphrase the explanation a little bit… CONTENT HERE.
“A control is a set of behaviors defined in code, NOT what you see on the screen. (Eg a button is really defined by a click behavior, not a grey rectangle.) What you’re seeing rendered on the screen is not “the control”; it is the result of interpreting / processing a Template for that control. Styles are a collection of desired values applied to behaviors or properties.”
This camp was also unique in that I was able to volunteer some time to help organize the event (I coordinated the day’s schedule and pulled together the syllabus content as well as the review forms.) Seeing things from behind-the-scenes provided an interesting point-of-view. Many thanks to Pat Tormey and the rest of the organizing crew for pulling the event together.
I also have to mention a couple of upcoming related and worthy events that unfortunately I cannot attend for personal reasons – the New England GiveCamp (June 11-13), and the Connecticut Code Camp (June 19).
As always, many thanks to my wife, kid, and cats for putting up with me in the weeks leading up to the event.