Results 1 to 3 of 3

Thread: Install in an install?

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default Install in an install?

    Friedrich,

    I have an application meant for only administrators and that the install (and web
    update) work perfectly. One of the requirements for this project is a child
    application that displays a very limited amount of information to all employees,
    its really a subset what the administrators see. It is its own stand-alone
    application.

    I can see two ways to install this:

    1) Include it in the main install (which includes web updates), which when done,
    does another install (or copies it to a common staging area). The advantage is
    that I only need 2 install projects instead of 4.

    2) Make a separate install (and web update) for this child application. Advantage
    here is that it keeps my main install projects cleaner and easier to maintain.
    But its two new install projects.

    For now, since we are in the testing phase, I'm just using one install project, so
    the they can test the employee application in a controlled environment. Later,
    we'll roll it out for the employees.

    Any advice?

    --
    Russell B. Eggen
    www.radfusion.com
    Clarion developers: www.radfusion.com/devs.htm

  2. #2

    Default Re: Install in an install?

    Russ,

    >
    > Any advice?
    >

    What about a .sb7 project that can generate different outputs (e.g. a
    "setup_admin.exe" and a "setup_child.exe")? The big advantage is that you
    only have to maintain a single .sb7 project and you can compile both
    applications.

    Similar to this:

    http://www.lindersoft.com/forums/showthread.php?t=11315

    http://www.lindersoft.com/forums/showthread.php?t=11316

    Friedrich

  3. #3

    Default Re: Install in an install?

    The admin setup is constant. The wildcard is the child setup. I'm thinking of a
    SB project that installs an install. That install could then be copied to a
    common folder and run from there for all workstations. The admin install produces
    an administrator program that sets up all the data. The client does not have that
    ability, it consumes the data the admin produces.

    The admin runs on only one workstation (which could include the child). All other
    workstations are child install only.

    Of course this is the initial install (for both). After that, the web update is
    quite sufficient for the updates for both programs. Don't yet need to build this,
    just thinking ahead.

    --
    Russell B. Eggen
    www.radfusion.com
    Clarion developers: www.radfusion.com/devs.htm

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •