Update Packs - Protect original setup.exe files?
Re: Update Packs - Protect original setup.exe files?
Great!
Aviv Giladi
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
-
Obliterator
- Posts: 53
- Joined: Fri May 01, 2009 11:54 am
Re: Update Packs - Protect original setup.exe files?
Maybe I misundertand, but maintaining copies and folders by hand sounds like hardwork to me!
Just use a version control system! Then endlessly overwrite without worry.
The binary scripts IA produces can be checked in - just like source code.
As binary files, these are hard to read/compare in a version control system.
But the good news is IA also saves text versions of your scripts alongside the binary files (presumably for this very reason!).
So the version control can track both file types and you can read and compare the text ones.
Simply create and checkin the first version of your script.
Build your setup and checkin the build.
Update your script for the next version.
Rebuild.
Check in your changes and new build.
Repeat forever!
With version control, you can easily see exactly what changed between each version in your scripts (or from version 1 to version 9 for example).
Should you ever need to recall a particular version of your script or setup.exe or msi you can do so! (together with info about when you released it, notes you put with it at the time, etc).
Version control is very efficient as it only stores the incremental changes between your builds.
And you can control your source code whilst your at it!
I really can't stress the importance of version control enough in this day and age.
For version control, I would recommend taking a look at Git with GitExtensions or TortoiseGit.
Git is free and doesn't require a server. You can just use it locally.
Just make sure you backup your repository to be sure.
Of course, if you work as part of a team you can use a server or free/cheap service like projectlocker.com
Just use a version control system! Then endlessly overwrite without worry.
The binary scripts IA produces can be checked in - just like source code.
As binary files, these are hard to read/compare in a version control system.
But the good news is IA also saves text versions of your scripts alongside the binary files (presumably for this very reason!).
So the version control can track both file types and you can read and compare the text ones.
Simply create and checkin the first version of your script.
Build your setup and checkin the build.
Update your script for the next version.
Rebuild.
Check in your changes and new build.
Repeat forever!
With version control, you can easily see exactly what changed between each version in your scripts (or from version 1 to version 9 for example).
Should you ever need to recall a particular version of your script or setup.exe or msi you can do so! (together with info about when you released it, notes you put with it at the time, etc).
Version control is very efficient as it only stores the incremental changes between your builds.
And you can control your source code whilst your at it!
I really can't stress the importance of version control enough in this day and age.
For version control, I would recommend taking a look at Git with GitExtensions or TortoiseGit.
Git is free and doesn't require a server. You can just use it locally.
Just make sure you backup your repository to be sure.
Of course, if you work as part of a team you can use a server or free/cheap service like projectlocker.com