Results 1 to 11 of 11
  1. #1
    Silver Lounger
    Join Date
    Jun 2002
    Location
    Cheadle, Staffordshire
    Posts
    2,177
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Distribution Package (VB6)

    I'm close to completing this project and wondered which method would be better for deploying the application.

    I use certain OCX controls : MSMAPI32.OCX , PDF.OCX, COMDLG32.OCX to name just a few.

    Do I use VB Package and Deployment, which collects the dependancies and installs them, or
    Do I use another installation package and what are the guarantee's all my controls are recognised and installed to the
    correct destinations ?

  2. #2
    Silver Lounger
    Join Date
    Jun 2002
    Location
    Cheadle, Staffordshire
    Posts
    2,177
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Distribution Package (VB6)

    I've had a quick look at Installshield for visual basic c ++ which is part of my VB package.

    I've not looked into this program before so have played about with the wizards.
    I followed the help files which starts:

    Take advantage of the project wizard.
    (Easy to follow)

    Then it states to use the "Media Build Wizard", again easy to follow.

    What confuses me, is I can see the project in the project window, I've selected CD as the media, but
    where is the Setup file to copy to the CD ?

    After following these two steps as above, how do I create the setup disc ?

  3. #3
    Silver Lounger
    Join Date
    Jun 2002
    Location
    Cheadle, Staffordshire
    Posts
    2,177
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Distribution Package (VB6)

    I have my application as a setup file using the Package & Deploy wizard.

    I installed the program to 8 PC's at our head office, no problems seemed to happen.

    One PC basically refused to boot after the install.

    I narrowed it down to the DLL files installed which were dependancies of the applications InstallShield (I think).

    The files:
    ASYCFILT.DLL
    OLEAUT32.DLL
    OLEPRO32.DLL
    STDOLE2.TLB

    Seem to be the offending culprits.
    My package is created on an XP machine.
    When installing to Win98 these files are part of the installation.

    I found an article from Microsoft which listed a download utility " MCREPAIR.EXE " which fixed the files.

    For future ref, can I disable these files in P&D so not to cause anymore issues.
    I would rather have a smoother install than the one I have now.

    Is there an updated installShield I should be using instead ?

  4. #4
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Distribution Package (VB6)

    Aren't some of those files OS dependent?
    If so, I'd expect problems installing XP version on Win 98.

  5. #5
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Distribution Package (VB6)

    I have those files on my Win2k machine, all with the same June 2003 date and version number, but I don't have InstallShield installed on this PC.
    Charlotte

  6. #6
    Silver Lounger
    Join Date
    Jun 2002
    Location
    Cheadle, Staffordshire
    Posts
    2,177
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Distribution Package (VB6)

    Howard, Yes this is the problem I am having at the moment.

    If they're OS dependent, Do I really need to have them within the package ?

    I managed to edit the Setup.lst and remove the lines which installed them.
    But in my actions, is this wise ?

    Charlotte, I thought the P & Deploy was installshield !!

  7. #7
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Distribution Package (VB6)

    If you're talking about the wizard that comes with VB6 Pro or with MOD, then no, it isn't. InstallShield and Wise are 3rd party applications that build industrial strength setup packages and allow you to script the behavior of the installer to a faretheewell.
    Charlotte

  8. #8
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Distribution Package (VB6)

    Most of the VB 6 stuff that I have distributed requires only the installation of a DLL, so I have manually rolled my own "setip programs.

    I do not even try to distribute run-times.

    Most of the newer OS and recent Office versions automatically install the critters.
    If not, folkes can download the needed run-times frm MSFT.

  9. #9
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Distribution Package (VB6)

    That leaves it up to the victim ... that is, the user ... to make sure they have the correct runtime version on their machine. Isn't that a little iffy for a critical application?
    Charlotte

  10. #10
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Distribution Package (VB6)

    No worse than an app such as Office or Easy Media Creator or ..., requiring that a particular OS or SP or SR version be installed.
    Newer systems should already have the VB 6 runtimes.

  11. #11
    Platinum Lounger
    Join Date
    Nov 2001
    Location
    Vienna, Wien, Austria
    Posts
    5,009
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Distribution Package (VB6)

    Sounds like a good way to keep "repeat work" requests down to a minimum.
    Gre

Posting Permissions

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