August 2009 Blog Posts
I’m doing a presentation on Continuous Integration at the Perth .NET Community of Practice Thursday 3rd September. This is a completely reworked version of a presentation I’ve given to colleagues aimed primarily at .NET developers looking to start using CI. Details: Date: Thursday September 3rd, 5:30pm Venue: Excom, Ground Floor, 23 Barrack St, Perth Cost: Free
…then The Howard Years is a much better documentary than Liberal Rule.
In a recent project I’ve had to implement a feature I think is a good example of a separation of concerns at a small scale. This feature involves giving the user a choice from a set of items. The available items from which the user may select an option is determined by a couple of factors. First there is a pool from which they may draw items. Users will preferentially get only those items directly associated with themselves if any are available. If no items are associated with the user then they get those associated with their user class....
On my current project we’re building multiple websites that share the majority of their logic but each have requirements relevant only to their target audience. This means we need a way to configure the common elements to behave appropriately to each scenario. This post discusses the mechanism I’ve chosen to do this. In building this mechanism I had a number of goals: Minimal Duplication It was not acceptable to simply duplicate whatever logic needed to vary. Whatever mechanism I chose has to keep as much logic common as possible to constraint development cost and ensure...
Further to the discussion that Rhys Campbell and myself have been having regarding interfaces, Lee Campbell has stepped in with a discussion of interfaces primarily related to Unity. Well worth a read, and I like to think somewhat of a justification to go download StructureMap.
When implementing services there are a number of practices I like to adopt. I have already discussed the use of interfaces to define the service contract. This post is to discuss the granularity of the contracts in a system. In all but the most trivial of systems multiple service actions will be required. In providing these actions we can choose a position on a continuum. At one end we have a single contract that has all the actions as methods. At the other end we have a separate contract for each action. In between we have contracts that provide...