Programming

Inspired by Scott’s post Hanselminutes – This is usually the podcast that helps to clarify some topic I had been meaning to learn more about. Sometimes a bit too focused on the web end of the spectrum, but still a solid source on what is out there and what is coming up.

A few weeks ago I read the blog post Git and command-line fear by James Gregory . He argues against the common Git on Windows complaint of poor Windows support. While I appreciate James’ position that this is not entirely true, and that most people do associate Windows support with GUI based tools or Visual Studio integration, I do disagree with his assertion that command line tooling is a valid use case.

Edit: Updated link at GitHub. github logo I have finally found an online code sharing site to post my open source code to – Hazware Unity Extensions on GitHub . I posted all of the source code for my Type Tracking Unity Extension there, and decided to follow the Ninject model for licensing – I dual licensed it as MS-PL and Apache, so go enjoy and help me make it better.

In my efforts to experiment with WPF, I decided to try the always popular WPF sample of an irregular or custom shaped window. I had set out the following goals for this sample:

WPF Demonstration Application For the past few years Microsoft has been pushing WPF as the future user interface framework for .NET. During that time I have seen numerous demos and presentations showing amazing user interfaces. They would describe the new model of separating the designer from the developer, and how successful they were. I would usually ask two questions as a response. First, how many designers and developers were involved. Second, how close to the original time and resource estimate was the actual effort. The answers to this would be one of the main reasons I have not yet embraced WPF.