At 02:02 PM 6/22/2009, you wrote:
Here comes the gum! I have a call thru to John Minyo and was going
to ask first thing: The PDF file mentions including the "product
executable". So I assume that means this is to distribute a
compiled .exe file? That if you plan on selling a complete RBase
software installation with it that RBInstaller wouldn't be
applicable? Looks like you would save the installatin files to a
CD that you would send out? I didn't understand where the end user
would be installing your program -- do they get to choose the target
directory or do you specify a directory to create?
Just simple questions like that. It would be interesting to see a
video clip of how the installation setup.exe would operate...
Karen
Go ahead and gum up the list! I would like to know more about this
and maybe others would also. The PDF didn't answer all my
questions, and I am not sure what questions to even ask!
Karen,
The product executable refers to the actual program that the
installer package will be installing. For example, if the product
being installed is Adobe Reader, the product executable would be
"AcroRd32.exe". For the R:BASE 7.6 for Windows install package, the
product executable would be "RBG76.exe". In the case where an R:BASE
Developer purchased R:Compiler and created their own executable,
their custom "exe" would be the product executable.
For any program installation where multiple files will be distributed
into multiple locations on a computer, an installer package will
likely be used. Installer software programs also offer additional
settings like adding a shortcut to the desktop, listing the program
under "Add or Remove Programs" and more. If a program installation
required very few options, a self-extracting archive executable may suffice.
The end result of the installer project, Setup.exe, can be made
available for download or provided on a CD media. The option is up to
the software developer/distributor, and of course is based on file size.
When building the installer project, settings to specify the default
installation folder are provided. An "Allow Browse" check box is
available to allow users to alter the default installation directory
where your product will be installed. If users do change the folder,
you must reply on using the registry to store and reference the new
folder in order to apply any product updates.
John
