Get a Customized Plan

The Fairway Technologies Blog

February 13, 2019 | Paul D. Sheriff

Build WPF Screens Using Inheritance and Aggregation

If you have a WPF screen that is made up of two of more "sections," where each section has its own unique functionality, you might want to consider breaking each of those pieces of the screen into individual user controls and individual view model classes. This will help you build, run, and test each component. You can then aggregate the user controls into one control and inherit from one view model to the other to bring them all together. In this blog post, you are going to build upon the sample created in the post entitled "Basics of MVVM in WPF." Read and download that sample application to follow along with this blog post.

February 6, 2019 | Paul D. Sheriff

Basics of MVVM in WPF

In this blog post, you learn how easy it is to use the Model-View-View-Model (MVVM) design pattern in WPF applications. This blog post is a step-by-step illustration of how to build a WPF application to display a list of users. You are going to perform the following steps.

January 16, 2019 | Paul D. Sheriff

iTunes Player Part 1: Read Songs From iTunes

Have you ever wanted to retrieve the list of songs from your iTunes library? Getting songs from iTunes is not easy. In fact, since Apple stopped supplying their COM component for reading from their iTunes library, about the only way to get song data is to export the library into an XML file, then parse the XML. In this blog post, you are going to learn to parse the XML using the classes contained in the System.Xml.Linq namespace.

December 12, 2018 | Paul D. Sheriff

A Message Broker for XAML Applications

In any application, you want to keep the coupling between any two or more objects as loose as possible. Coupling happens when one class contains a property that is used in another class or uses another class in one of its methods. If you have this situation, then this is called strong or tight coupling. One popular design pattern to help with keeping objects loosely coupled is called the mediator design pattern. The basics of this pattern are very simple; avoid one object directly talking to another object, and instead use another class to mediate between the two. This class is called a message broker. The purpose of this blog post is show you a simple approach to using a message broker in your XAML applications.

November 28, 2018 | Paul D. Sheriff

An Architecture for WPF Applications

In this blog post, you learn to create a standard architecture for your WPF applications. You learn what common classes you need, what kind of library to put those classes into, and how each of the libraries are referenced from your main application.

New Call-to-action
New Call-to-action