Results 1 to 3 of 3

Thread: NSIS/VB6 - Help Needed

  1. #1

    Thread Starter
    Fanatic Member modpluz's Avatar
    Join Date
    Sep 2005
    Location
    Lag, NG
    Posts
    633

    NSIS/VB6 - Help Needed

    hi guyz,

    pls how can i make NSIS get all the required files(dependencies) for my VB6 application on compile.
    If you want the rabbit to hop, move the carrot - Paul Kellerman(Prison Break)

    onError GoTo http://vbforums.com



    My Bits:
    VB6: Change Column Name in MS ACCESS

  2. #2

    Thread Starter
    Fanatic Member modpluz's Avatar
    Join Date
    Sep 2005
    Location
    Lag, NG
    Posts
    633

    Re: NSIS/VB6 - Help Needed

    anybody pls...
    If you want the rabbit to hop, move the carrot - Paul Kellerman(Prison Break)

    onError GoTo http://vbforums.com



    My Bits:
    VB6: Change Column Name in MS ACCESS

  3. #3
    I'm about to be a PowerPoster! kleinma's Avatar
    Join Date
    Nov 2001
    Location
    NJ - USA (Near NYC)
    Posts
    23,373

    Re: NSIS/VB6 - Help Needed

    Unless there is some utility you can use you will have to figure that out youself.

    One method you can use, is to create a package using the VB PDW (package and deployment wizard) which makes a setup.lst file. This file will contain good information on what files need to be distributed with your app (open it in notepad)

    However it usually comes down to this:

    1) VB6 runtimes, these HAVE to be distributed. Windows 2000 and up come with them installed with the OS, but prior systems do not, and you are better off including them no matter what because they are on VB6 SP6, and the ones that came with 2000 and XP are not as new. You can install these individually, but you can also get a self extracting, self installing exe that is about 1 MB and contains all 6 runtime files needed. (search MS website to find this download)

    2) if you use a database in your app, you need to include MDAC (also can be downloaded from MS), if the database you use is Access, you will need to distribute JET drivers as well (again, MS download)

    3) any 3rd party OCX, DLLs that you use (3rd party includes any Microsoft ones, basically any references or components you added to your project while developing it) need to be included as well, and the installer needs to register them during installation (which should be a feature of the installer)

    I haven't used NSIS, I use INNO setup, but I believe they are similar.

    Last but probably the most important step, test your installation on a FRESH windows install, for as many operating systems as you can (or intend to support)

Posting Permissions

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



Click Here to Expand Forum to Full Width