Is there a technique for determining the files, libs, etc. that absolutely have to be included in an install package? For example, if there are a group of desktops that all have Win 2000 with Office XP Professional, the things are already going to have a bunch of DLLs that are required by any VB app I might wish to install.
I'm concerned about including a file from my development environment that overwrites a perfectly fine existing dll and trashes the workstation.
I've been using the Pkg & Deployment Wizard and am considering Installshield or Wise, but I'm not sure that addresses the issue.
Thanks -
I'm concerned about including a file from my development environment that overwrites a perfectly fine existing dll and trashes the workstation.
I've been using the Pkg & Deployment Wizard and am considering Installshield or Wise, but I'm not sure that addresses the issue.
Thanks -