Over the last few years, the practice of Test-Driven Design and Behavior-Driven Design has increased […]
Wrapping up the StructureMap Automocking Container
UPDATE: I apologize…the original wrapper did not allow injected dependencies. I have fixed this bug and updated the sample.
I have been using StructureMap.AutoMocking with MSpec (Machine.Specifications) and Rhino.Mocks for a few months now. Although I am very comfortable with the patterns that emerge from using the frameworks together, introducing StructureMap.Automocking to other developers is sometimes challenging. I decided to wrap the details of the container to make the intention clearer and explanation easier. I have started using this wrapper in my projects, and have found it makes building up specifications more efficient in my daily coding.
State Pattern, Enumeration Class and Fluent NHibernate (Oh my!)
Recently, I needed to change a basic enumeration into a full-fledged state pattern. After getting all my domain classes updated, I began reviewing the persistence layer. And I hit a wall. I wasn’t sure how I wanted to update my Fluent NHibernate convention to persist the current state.
AutoMapper Introduction and Samples from NETDUG
In September, Cory Isakson and I presented AutoMapper to the Boise .NET Developer User Group […]
Implementing Team City for .NET Projects, Part 5: Deployments
My apologies to all those who have been waiting for the deployment scenario ? I […]
Implementing TeamCity for .NET Projects, Part 4: Using Build Scripts
For more information on this series, please see the introductory post.? This post also assumes […]
Are you ready for Portland Code Camp?
Portland Code Camp is next Saturday. Over 60 sessions have been submitted so far from […]
Implementing TeamCity for .NET Projects, Part 3: Running Tests, Nightly Builds, and Creating Artifacts
For more information on this series, please see the introductory post. This post also assumes […]