Part 0: stating my intent Part 1: seams, patterns, tdd Part 2: testing styles and credentials Part 3: architecture and project structure Part 4: a change of direction Part 5: value converters

Table of Contents Application Architecture I'm going to back up and bit discuss my overall approach to structuring this WPF project. So far the solution consists of four projects: ChumChase is the actual WPF project. FriendFeed is the official .NET api I downloaded from here , and patched so that...

Table of Contents So let's get back to this whole building a WPF application thing. A number of things went down since my last post: I was out sick with a stomach bug for few days, my infant son caught the same bug and subsequently we spent a few days in the hospital (he's fine now, it was nothing...

Table of Contents I actually meant to say in my last post that I had investigated the API options for FriendFeed and they have a C# wrapper already available here . It's packaged up in a single download with its Python and PHP counterparts. Unfortunately, it has compilation errors. I fixed the errors...

Table of Contents In a rather indirect way, I was inspired by a commenter on one of Scott Hanselman's posts to begin a series that walks through building a WPF application from start to finish. We did this for four different applications in our book , but those where targeted to demonstrate particular...

Oren always amazes me - I think he is psychic! Whenever I have a problem, I almost always find Oren blogged about it a few days before - and today's bugbear is a perfect example. I started the day off with a really weird timeout exception in WCF. The code was just fine apparently, and I spent a very...

As it sort of came up via a previous post, and on the altdotnet mailing list ... I thought I would share a little secret with you ... abstracting out legacy systems can be pretty darn simple with a bit of Reflector magic! Step One: Get Reflector You can download it here if you don't already have...

Update: Re-published from old blog I found a need yesterday to test some code in particular security contexts. After some (as always) prompt guidance from the altdotnet mailing list, I had the (as it turns out) all too simple solution. xUnit includes an attribute for this, but as I'm using NUnit...

Over the past few weeks I have worked on a few products for my client that will be used as API's.  These API's will be used by either their own (external) clients or other internal departments.  Working on these projects made me think about testing in a little different light compared...

I finally got around to upgrading to the most recent version of NUnit recently (Yea I know, bout time) and found out that there is a new way of doing assertions.  The new model is referred to as the 'constraint' model and follows a more fluent style interface.  Below are some examples...