Files to include in installer 1

[Schroeder]

When creating an installer, is it wise to include every file upon which your program depends? I'm running the Package & Deployment Wizard to create a dependancy file. I'm using Inno Setup to create the installer. Should I go down the list of files that the P&DW found and include them all?
This worries me because when I used to use the P&DW and accept its entire list of dependancies, I occasionally hosed systems and had to reinstall Windows to set things straight. Since then, I've been running uninstalled .exes, waiting for them to crash and, only then copying over just enough files to prevent repeat crashes.

 

[Schroeder]

I should add: Inno Setup says that I shouldn't copy any versions of COMCAT.DLL, COMCTL32.DLL and CTL3D32.DLL. I notice that the P&DW suggests copying COMCAT.DLL. Maybe this has been my problem in the past?

 

[CCLINT]

No no. Use the list that P&D gives out.
Three things you need to make sure you do:

1. Make sure the developers PC is up to date with to most recent service pack for the operating system.

2. Make sure you use the latest Service pack for VB6.

3. Make sure that any third party controls added to the project are up-to-date.

If you run into problems during the setup on the client with any system files, the easiest thing to do is have most recent service pack for the client's OS installed.

Any other problems that you may have may be coming from other programs - with may need to be upgraded.

If you follow these points, you shouldn't have a problem with the OS or the VB exe that you are installing. If some other product doesn't work anymore, then that product may need to be updated......

 

[Schroeder]

CCLINT,
Thanks for the reply. I'll follow your advice but I'm still a little bit worried. When I ran into trouble with the P&DW, I can say that points 2 and 3 were covered. I'm developing on 98 SE and, to my knowledge patches have primarily been security fixes.
You say problems that I'm likely to run into are probably related to other, out of date programs. Twice, upon finishing a P&D created install, Windows itself quit working. As soon as it booted, Explorer.exe (or some other critical program) crashed. This happened on two different machines. I've never had an installer other than mine do this to a machine before.
I don't mean to challenge your answer. I have no doubt that you have more experience in this department than I. I'm just scared. Up 'til now, I've been putting my programs on machines to which I have regular access and I've been able to handle any trouble. Soon, I'm going to be distributing to a client and I don't want to crash their Windows before my program even has a chance to crash on its own.

 

[CCLINT]

The P&D will not replace any files that are newer on the client. It will however, update the client with newer system files.
If you had trouble with th OS itself, then something else may be causing it. With thousands of installations of some major programs, the main issues that I have had to deal with concerned third party programs such as print manager drivers and AV software,getting in the way, or other programs not working any more. Whether it was the OS or another program, in almost all cases a correct update of the OS with a service pack, or service pack for the other programs, or newer drivers, corrected the problems - These would be needed sooner or later anyways.

I'm speaking W98 and upwards. Under W95 there were several other issues however, but most of these were also easily corrected.

Why not upgrade to the Visual installer (from MS FOC). But, internally, this works like most other installation programs. The actual verification, installation, copying and registration of system files are pretty handled the same way.....