Best Way From Test to Production?

[carvster]

Thanks everyone for your comments/help. Sorry for taking a while to get back here.

Originally Posted by princeton

Every line that I modify (vb file) I wrap with the following:
//==========================\\
// == [ HACK A - GTP ]
enter code here
// == [ 00-00-2005 ]
//==========================\\

This allows me to search for 'modified' sections at a later time with a script that I wrote. The script searches for specific phrases (ie. 'hack a', 'GTP', etc) in a file and displays any file(s) that have been modified. From there, I just have to look at the files for the above comments (wrap). This works online/offline.

This allows me to quickly document my modifications. (I document every modification that I do.)

This is a great idea. If the mod requires a change rather than an addition, do you leave the original phrase included in comments? One problem I found is when several complex mods are installed subsequent and they change the same portion of the script.

Perhaps the solution is commenting out the original phrases tagging them as original and then commenting out each subsequent mod change, thus leaving a trail for that particular phrase would help to keep track. That would add a lot of code though. I suppose I could keep an archive copy of all the changes and just single reference to the previous hacks in the production file.