I would probably (and if anybody has another suggestion please jump in) set it up this way.
Now this is assuming a date based version number like 20060519 but anything will do.
And we have the folder
D:\Revision\20060519\App\
D:\Revision\20060519\My Documents\
D:\Revision\20060519\Local Settings\
Put all the relevent files in each folder and have a COMPLETE copy for each and every version... really i have found this is worth the duplicate files. It makes it sooo much easier when it comes to updates.
Then you have 3 folder references (with sub directories if you need). The destination folders don't have to be structured the same way so
D:\Revision\20060519\App\ "installs to" %AppDir%
and so forth.
Then you can use the #VERSIONTABNAME# macro.
Also i use an patch file name like "MyApp#NEWESTVERSION#Update.exe" so it automatically creates the filename "MyApp20060519Update.exe" without any intervention. Such a great feature i can never get it wrong!!
Now this is assuming a date based version number like 20060519 but anything will do.
And we have the folder
D:\Revision\20060519\App\
D:\Revision\20060519\My Documents\
D:\Revision\20060519\Local Settings\
Put all the relevent files in each folder and have a COMPLETE copy for each and every version... really i have found this is worth the duplicate files. It makes it sooo much easier when it comes to updates.
Then you have 3 folder references (with sub directories if you need). The destination folders don't have to be structured the same way so
D:\Revision\20060519\App\ "installs to" %AppDir%
and so forth.
Then you can use the #VERSIONTABNAME# macro.
Also i use an patch file name like "MyApp#NEWESTVERSION#Update.exe" so it automatically creates the filename "MyApp20060519Update.exe" without any intervention. Such a great feature i can never get it wrong!!
Comment