So you want to build an installer?

[kweatherhead]

Greetings,

I realize that if 100 people discuss this, there will be at least 80 different answers, however I would hope that there could be an agreed upon, "general", standard to use, as a starting point.

What I am looking for is a "somewhat" detailed overview in an outline format (HowTo) for designing an installer, with regards to the order of doing things, for more than installing 1 EXE and a desktop icon. An outline of items, that would be in a "generally" expected sequence for a moderately complex installer, handling more than one module.

I understand that each project is different, but some of you here must have a basic approach that you use over and over again that address these issues and if you would be willing to share your recipe, it would be very much appreciated.


For example:

1 Upon Start-Up, verify OS and hardware, if necessary
a) Check OS Version, and Patch Level requirements
b) Check for Processor Family, if applicable
c) Check for RAM requirements, if applicable
d) Check for Minimum OS drive space for libraries that need to be put there


2 Check for Installer Security
a) Is installer still valid, not expired date wise
b) Is installer still valid, number of installs
c) Request S/N for a locked installer


3 Opening Screen

4 Check if a previous version exists?
a) Check Registry
b) Check Hard Drive, default location(s)

5 Determine if RunTime Environments exist
a) Dependentcies module validations
b) Other external program requirements

6 Ask User What they want installed

7 New Install or Update

(note: at this point I would expect different trails to exist, based on what type of operation you are doing.)
.
.
.

# install files...
# make registry adjustments
# display README
# cleanup and Exit !

etc...



While here on this subject, an outline... structure to handle updates and other maintenance, too.

Regards,
Keith

[jassing]

I have created installers for companies all over the world -- I have converted existing installers to suf7 -- with rare exception -- each one was different.

The owners/clients all had different requirements & expectations, so I don't see how this would "help" anything other than help you deal with managing multiple installers across product lines.

That said -- what works for you is what you should do.... But I don't think being hired to create an installer and say "this is how I do it -- it's my standard" will be a very happy thing to hear from a consultant....

That's just my $.02 on the subject...

[kweatherhead]

I have created installers for companies all over the world -- I have converted existing installers to suf7 -- with rare exception -- each one was different.

Understand that they could/*would* be more different than similar...

The owners/clients all had different requirements & expectations, so I don't see how this would "help" anything other than help you deal with managing multiple installers across product lines.

That said -- what works for you is what you should do.... But I don't think being hired to create an installer and say "this is how I do it -- it's my standard" will be a very happy thing to hear from a consultant....

That's just my $.02 on the subject...

I too am a developer. My backgound is Unix (Sun/HP) not Linux, and I have written *many* multi-platform installers in that environment. I have *not* done but a couple very small projects under Windows, though, and this project is slightly bigger than I had attempted to write a Windows installer for.

What I was looking for was a thought-process template, to make sure that I do not miss/skip any steps that I should be addressing. I am not saying that I want someone to write a "specific" installer for me, nor that I would use all steps or even most steps... but I would like to be sure they are at least considered in the design process. I not going to shove this on anyone and nobody is going to shove it on me, either.

Like I said up front, 100 people will do it *at least* 80 different ways, maybe more. I was wondering if someone had developed a "template" by which they start the process and had put the template steps in a reasonable order, and they were willing to share it.

Regards,
Keith

[jassing]

No template here -- I start with desired end results and work backwards.

Customer knows best.
Then figure out what technical steps need to be done
what files need to be installed (and where)

Everyone is different
for instance, one client didn't want the "path to install" changed if there was already another program installed; yet another didn't want it to change if there was a registry entry involved; yet another wanted the original (ie: upgrade) deleted if they changed the new install path, while migrating datafiles around....

Hard to come up with a template; sorry I'm not more help -- if you need help with doing the windows install -- feel free to PM me...