Install Cache Leaves Unsigned Executable Files

[mwhouser]

I am trying out the caching of the setup sources in a single file install.

I am noticing that it's leaving behind a number of executable files (DLLs, EXEs, etc.) that are not signed. This will cause Vista certification to fail.

Is it possible to cache the setup sources as an MSI instead of flat files?

If not, how can we make a vista certifyable install that allows modify/repait to work with a single file install?

Thanks,
...Matt

[MichaelNesmith]

I'm afraid your only recourse is to prevent setup source caching in that scenario. Files cannot be cached inside archives.

[mwhouser]

Ok. I'd highly suggest that this be an issue worth addressing in the future. I am sure we are not the only company needing an installer that can combine:
(a) Single File Install
(b) Modify/Repair functionality
(c) Vista Certification

...Matt

[MichaelNesmith]

It's not an InstallAware issue. Any installer which would cache files would run into this issue. Sign your files! Or, if they are runtimes, nuke the runtime folders post-install to ensure they don't get in the way.

[mwhouser]

The other installer used to cache the MSI and would access that during modify/repair.

All of our files are digitally signed.

The files being left behind are files like:

C:\\ProgramData\\...\\mWinRun.DLL\\mWinRunExec.DLL
C:\\ProgramData\\...\\mWinRun.DLL\\ansi\\Cabinet.DLL
C:\\ProgramData\\...\\mWinRun.DLL\\ansi\\msihnd.DLL

So you're saying it's safe to just delete these? And modify/repair will still work?

...Matt

[MichaelNesmith]

These are runtime installer files. Like I said, it will be safe to delete the whole folder. And no, even the other installer does not put runtime files inside the MSI