Chapter 14 -- Version Control

[Previous] [Next]

Chapter 14

Change is inevitable. Creating computer software is more like growing a garden than manufacturing a widget. Although a distributed program file is a static entity, the program itself usually changes ”even adapts ”over the course of its life. For example, developers usually change a program to correct problems or improve usability. When developers stop enhancing a product, it's often abandoned by users who switch to tools that are more in line with current business paradigms . It's a simple fact that you must improve your product or lose your customers. Although this constant change is good for users (and good for your bottom line), it creates a number of challenges for developers and project managers.

Projects in Microsoft Visual Basic are complex entities, often composed of dozens of source files. In addition, most projects make use of ActiveX controls and are distributed through the use of dedicated installation programs. As you make changes and distribute new versions of a program, it becomes exceedingly difficult to keep the entire process moving forward. For example, have you ever inadvertently compiled an older version of a form in a new program and ended up breaking what was once working? Also, you need to make sure that you add version information to your applications so that installation programs and adventurous users don't end up overwriting a program with a version that isn't current. And you need to have a solid backup plan to ensure that you never lose important program changes.

Goals of Version Control

---

The goals of version control include

• Compiling the most current and stable components
• Versioning all compiled programs
• Maintaining a history list of changes in versions
• Backing up project and other source files to prevent loss of work and time