A while back I posted some snippets for WPF here: WPF Snippets for Visual Studio . I've been wanting to update these for a while now and finally got around to it this morning. Here are the new snippets. basevm This is a snippet that effectively replaces the inpc snippet (although that is still included for demos etc). The primary addition is that of a SetValue method that actually checks if values have been changed before raising the PropertyChanged event. Here's what the snippet looks like. // TODO

Early this year we built a business application for order management for Northwind Traders on the Office and SharePoint platform using Visual Studio 2008 and Office & SharePoint 2007. If you missed them: Architecture of the Northwind Office Business Application OBA Part 1 - Exposing Line-of-Business Data OBA Part 2 - Building an Outlook Client against LOB Data OBA Part 3 - Storing and Reading Data in Word Documents OBA Part 4 - Building an Excel Client against LOB Data OBA Part 5 - Building the

O Microsoft SDK para o Facebook oferece suporte de desenvolvimento de aplicações em Silverlight , WPF , ASP.NET , ASP.NET MVC e Windows Forms, permitindo a fácil utilização de serviços através da API Open Stream do Facebook. Obrigada.

Trying to get the bindings right for a certain ControlTemplate I wanted to have for a TabControl lead me to an interesting observation on TemplateBinding that was not so obvious. In the TabControl's ControlTemplate, I wanted to have an inner ItemsControl binding to the templated TabControl's Items (and thus replace the default TabPanels). It ended up working with a RelativeSource binding like this: < ControlTemplate x : Key ="CustomTabControlTemplate" TargetType ="{ x : Type TabControl }">

In my last post , I told the story of a customer who asked for an easy way to make the Silverlight/WPF WrapPanel use all available space to spread its children out evenly instead of bunching them up together. The following sample shows off the default WrapPanel behavior on top - and my alternate BalancedWrapPanel behavior on the bottom: The default WrapPanel behavior fills each horizontal (or vertical) line as much as it can before moving on to the next line, but leaves any extra space at the end

The WPF text team has seen some people get confused about what units WPF uses when measuring text. Samer, a developer on the WPF text team, and I have created this post to try and shed some light on this subject. The first part of this post is very straight forward, whereas the end will only be useful for those of you who are extensively using WPF text APIs. General Units WPF supports multiple units for text measurement. The units that can be used are “px” (device independent pixels), “in" (inches),

Raw Touch Events Touch events are the equivalent of mouse events for multi-touch input. In WPF4, we’ve added touch events to UIElement, UIElement3D and ContentElements. Multi-touch events follow the same patterns as mouse events, with TouchDown, TouchMove and TouchUp, the Preview variants and TouchEnter and TouchLeave. Multi-touch events in WPF are hit-tested and routed through the element tree just like other input events. This is different from the low-level application wide touch event support

Yes, it’s that time of year again when March (and MIX) seem to be both in the distant future and almost upon us at the same time. The conference is billed as: “A 3 day conference for web designers and developers building the world's most innovative web sites.” But it’s even broader than that. If I understood Ray Ozzie correctly ( in the PDC keynote ) this is also where we’ll hear about developing apps for the next generation of Windows Phone and the Windows Live Platform. So it’s about Silverlight,

We get questions ranging from “will next version of Prism use MEF?”, “How can we use MEF in the current version of Prism?” to “would MEF replace Prism?”. My colleague David Hill just did a blog post that addresses many of these questions. Check it out here Excerpts from his blog post: First of all, it’s important to note that Prism and MEF are very much complementary technologies. MEF allows you to create extensible applications by providing support for automatic component discovery and composition.

I heard on twitter the other day (Yes, I now tweet occasionally. If you'd like to waste literally seconds of your day you can follow me at joshtwist ) that some folks at an Alt.Net UK event where giving P&P and Prism a rough ride. Specifically, they had some issues with the EventAggregator - citing Jeremy Miller's criticisms in this post Braindump on the Event Aggregator Pattern . I need to say up front that I really like the EventAggregator in Prism - it's one of my favourite bits. However,