How to use version control to track changes to script...
Posted: Mon Jan 16, 2006 4:23 pm
I use version control to track changes to all my development projects. This really helps me see the changes I made between releases and more easily avoid or track down bugs. With the new "Copy as Text" feature for InstallAware scripts, I've been able to make a text-file-friendly/human-readable version of my scripts. Anytime I make changes to an InstallAware script, I do this:
1. Select all the lines of my script, then I "Copy as Text".
2. I open a .txt file corresponding to my script (ie. if my script file is "script.mia", then I open a text file called "script.mia.txt").
3. I clear the file, then I paste the script fom the clipboard and save the file.
Now I have a human readable text file that corresponds to my script file, and I can see precisely what changes I made to my setup script by comparing this file with previous versions.
As a suggestion, it would be great if the above steps (1-3) occured everytime I saved the script (resulting in the text file being automatically kept up to date).
--Troy
1. Select all the lines of my script, then I "Copy as Text".
2. I open a .txt file corresponding to my script (ie. if my script file is "script.mia", then I open a text file called "script.mia.txt").
3. I clear the file, then I paste the script fom the clipboard and save the file.
Now I have a human readable text file that corresponds to my script file, and I can see precisely what changes I made to my setup script by comparing this file with previous versions.
As a suggestion, it would be great if the above steps (1-3) occured everytime I saved the script (resulting in the text file being automatically kept up to date).
--Troy
