Wiki

[[jayflowers]] JayFlowers Trace: » JayFlowers » jayflowers This page has moved and you will be redirected. jayflowers.txt · Last modified: 2006/05/04 14:31 by jflowers

[[doublersupport]] JayFlowers Trace: » doublersupport Google Groups Subscribe to Doubler.User — — — Email: Browse Archives at groups.google.com doublersupport.txt · Last modified: 2006/04/23 22:18 by jflowers

[[refly]] JayFlowers Articles :: Software Projects :: Works in Progress Description Refly is a code generation library, a wrapper around the .NET Framework’s CodeDom. It was originally written by Jonathan de Halleux. One of the goals of this project are to have simpler interfaces than the CodeDom, as well as cohesive. This should make for a library where the user does not need to refer to documentation to know how to use it. ...

[[software_projects]] JayFlowers Articles :: Software Projects :: Works in Progress ASOGS Serializer MbUnit CI Factory Doubler MbUnit Extensions Common nAnt Tasks Refly software_projects.txt · Last modified: 2006/04/23 16:01 by jflowers

[[mbunit_extensions]] JayFlowers Description These extensions are not included in the MbUnit project. I have released them separatly so that they may be used with existing versions of MbUnit. There is only one type of fixture, ObjectFixture. TestWithEachObject is the accompanying test method attribute. The ObjectFixture provides a, just one, parameter to the test method. The parameters can be provided by one of three providers, FactoryObjectProvider, FormattedObjectProvider, or XmlObjectProvider. Videos FactoryObjectProvider Download mbunitextensions.zip ...

[[mbunitextensions.factoryobjectprovidervideo]] JayFlowers mbunitextensions.factoryobjectprovidervideo.txt · Last modified: 2006/04/08 20:40 by jflowers

[[communication_lines_patlet]] JayFlowers Trace: » communication_lines_patlet Need to write this one. communication_lines_patlet.txt · Last modified: 2005/10/31 13:06 by jflowers

[[development_workspace_patlet]] JayFlowers Trace: » development_workspace_patlet Context All developers and the Integration Build work in their own Private Workspaces yet there needs to be consistency between them. This pattern is a means to define the structure of the Private Workspace. Problem With many Private Workspaces how do you mitigate the chance that differences between them will cause bugs? Solution Define a structured workspace and location for it in private environments. Allow for variation in the content and not the structure. ...

[[integration_build_patlet]] JayFlowers Trace: » integration_build_patlet Context All developers work in their own Private Workspace so that they can control when they see other changes. This helps individual developers make progress, but in many workspaces people are making independent changes that must integrate together, and the whole system must build reliably. This pattern addresses mechanisms for helping ensure that the code for a system always builds. Problem How do you make sure that the code base always builds reliably? ...

[[task_level_commit_patlet]] JayFlowers Trace: » task_level_commit_patlet Context An Integration Build is easier to debug if you know what went into it. This pattern discusses how to balance the needs for stability, speed, and atomicity. Problem How much work should you do between submissions to the version control system? How long should you wait before checking files in? Solution Do one commit per small-grained, consistent task. task_level_commit_patlet.txt · Last modified: 2005/10/31 13:04 by jflowers