Software Coding Standards
June 15, 2008
Coding standards are a very important aspect of software development. Coding standards is not just about naming standards, but also includes using a standard pre tested and robust set of common core libraries, where appropriate using simple tested and tried design patterns, and quality control, to ensure standards are enforced.
Some of the main benefits of using set of coding standards, is to improve the quality of software delivered and uniformity of code which assist with maintainability. It is often said that if you cannot tell who has written code in an applications code base then that is a good start. Defining standards early, appropriate to the specific project and software and tools used, is important to help reduce the amount of refactoring that will need to be done later in the project at a greater cost.
There are many pre-defined examples of coding standards, which can be used as a starting point for your own standards, applicable to your own specific project. Tools can assist in implementing standards, such as Resharper and to enforce these standards, such as FXCop.
Deployment Process
June 4, 2008
A major benefit of using a build and deployment process is that it simplifies deployments and ensures consistency of code through all environments, from development and test environments right through to the production and disaster recovery environments.
The code base is deployed with a single-click approach where the application, version number and environment is specified. Because there is little to no manual intervention you can be assured that all evironments with the same version will have the same code.
Build Process
May 28, 2008
The heartbeat of any Buildmasters project is our continuous build process. This combination of technologies allows a team of developers to develop and unit test the code confidently and in isolation whilst the entire process of integrating the completed components is automated on our ‘Build Machine’.
Each time a developer checks in a piece of code the Build Machine detects the change in our Subversion Source Control System and kicks off an automated build of the entire project using Visual Build Pro. We follow a Test Driven Development (TDD) approach, which means that each code component that is checked into source control is accompanied by a number of unit tests also. The automated build compiles the code for the new component and the unit tests and then runs the tests. Read more

