My software has about 20 .dlls that get installed into many different folders. From everything i've seen, InstallShield can't have a component install to more than one location.
How do you experts handle something like this?
My install package is getting extremely large and slow because of this.
I was considering making 1 component with the files, install it to a temporary area, then writing a custom action to copy these files to the necessary folders. This seemed a bit cheesy though.
BTW, i'm using instalshield 2009 installscript msi project.
My software has about 20 .dlls that get installed into many different folders. From everything i've seen, InstallShield can't have a component install to more than one location.
How do you experts handle something like this?
My install package is getting extremely large and slow because of this.
I was considering making 1 component with the files, install it to a temporary area, then writing a custom action to copy these files to the necessary folders. This seemed a bit cheesy though.
BTW, i'm using instalshield 2009 installscript msi project.
It's not the fault of IS. The MSI SDK best practice requires you to make a component of each .dll, .exe etc. Can't you put the shared DLL in SystemFolder, marked permanent and shared for this purpose?
