While refactoring ClipFlair code to use MVVM (Model-View-ViewModel) pattern, I came across the XAML error “Object reference not set to an instance of an object.”, shown in Visual Studio when trying to bind to my ViewModel (accessed implicitly, being set as the DataContext of the XAML control) for a property named Source. I have settled [...]

Just came accross a runtime error message that troubled me a bit to resolve while adding Prezi-like content scaling functionality in ClipFlair‘s FloatingWindowHostZUI (ZUI = Zoomable User Interface) container. I had added the following: /// Identifies the <see cref="FloatingWindow.Scale" /> dependency property. /// ...

While adding some properties to the back panels of ClipFlair windows, I came upon the issue of how to space items in a StackPanel. A Padding property is missing from multiple item containers (only single content controls have such), but a nice solution is described at: ...

In this post I will provide you with hands-on examples on how to retrieve data from a WCF Data Service and bind the data to WPF data bindable controls that reside inside a WPF window.The client application in this case will be a WPF application again. (read more)

In this post I will not be investigating at what some people call the “Windows single technology applications” which basically means that we build WinForms apps for the windows operating systems using only Windows Forms controls or alternatively build a windows WPF application using only the built-in or 3rd party WPF controls. (read more)

differences between wpf and window forms. A small example using xaml, expression blend and visual studio.

I have been asked from some people to write a simple post regarding the younger and more flashy brother of window forms. WPF is about 1 years old now and gaining ground on developers for building next generation window applications.