NewsArchive
02-22-2008, 02:28 AM
This is not a problem in SB but a problem with me <g>
I have 2 installers. One is the initial install with everything in. The 2nd
is an upgrade install. After v1 has been released I include all extra files
in the v1.1 upgrade install. No problem there.
However in v1.2 I clearly need to include all the files in both v1.1 and
those new to v1.2 as someone might upgrade direct from v1 to v1.2 and skip
v1.2
My problem is that I am now on v8.3 and the upgrade installer has just about
become to all intents and purposes the full install. i.e. I always need to
provide the applications files, all 3rd party files (as they are always
being updated) etc.
Now, all these upgrade files of course are included in the master full
install of course.
So would I not be better to just have one single installer that recognised
if an existing application was there and if so did what was necessary? But
if I do, does this not take away from the patch methodology where installs
are smaller?
It would seem to me that I cannot do both at the same time other than to
limit upgrades to a condition whereby they are dependent on having a
previous version installed.
Bottom line, many of my clients never upgrade for some time then all of a
sudden want to be on the latest version , and so will always be skipping
several interim version upgrades.
Is there any easy solution to this?
TIA
John Fligg
I have 2 installers. One is the initial install with everything in. The 2nd
is an upgrade install. After v1 has been released I include all extra files
in the v1.1 upgrade install. No problem there.
However in v1.2 I clearly need to include all the files in both v1.1 and
those new to v1.2 as someone might upgrade direct from v1 to v1.2 and skip
v1.2
My problem is that I am now on v8.3 and the upgrade installer has just about
become to all intents and purposes the full install. i.e. I always need to
provide the applications files, all 3rd party files (as they are always
being updated) etc.
Now, all these upgrade files of course are included in the master full
install of course.
So would I not be better to just have one single installer that recognised
if an existing application was there and if so did what was necessary? But
if I do, does this not take away from the patch methodology where installs
are smaller?
It would seem to me that I cannot do both at the same time other than to
limit upgrades to a condition whereby they are dependent on having a
previous version installed.
Bottom line, many of my clients never upgrade for some time then all of a
sudden want to be on the latest version , and so will always be skipping
several interim version upgrades.
Is there any easy solution to this?
TIA
John Fligg