Hello all,

This has been packaged up (vcredist_x86.exe downloaded, MSI extracted and MST created etc) however when it installs it seems to leave an admin install to C:\ - or D:\ etc if that has more free disk space - and the following is left behind after a sucessful install:

  • eula.1028.txt
  • eula.1031.txt
  • eula.1033.txt
  • eula.1036.txt
  • eula.1040.txt
  • eula.1041.txt
  • eula.1042.txt
  • eula.2052.txt
  • eula.3082.txt
  • globdata.ini
  • install.exe
  • install.ini
  • install.res.1028.dll
  • install.res.1031.dll
  • install.res.1033.dll
  • install.res.1036.dll
  • install.res.1040.dll
  • install.res.1041.dll
  • install.res.1042.dll
  • install.res.2052.dll
  • install.res.3082.dll
  • VC_RED.cab
  • VC_RED.MSI
  • vcredist.bmp
Installing manually via vcredist_x86.exe does the same thing. As usual a classy installer from MS....

Deleting the files post install is OK but if the app is then repaired via control panel they are restored again.

Registry InstallSource is value is C:\12e9a90d3037a845a91002 for an .EXE based install and Z:\Path To\Source MSI\ for the .MSI based install - so all as expected.

Haven't bothered digging too deep into the MSI, but does anyone else have any experience of this - did you just live with it?

Not really a big deal but it is annoying, I like to keep C:\ as clean as possible - and I can already hear users asking what the files are... [:'(]

Thanks,
Rob.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Deleting the files post install is OK but if the app is then repaired via control panel they are restored again

I have packaged different version of MS VC++, those files are not required and can be deleted.
Answered 06/19/2009 by: mekaywe
Brown Belt

Please log in to comment
0
Sure it isn't an issue for C++ 2005 - no problem to script the deletion of the files but it's still annoying me.
Answered 06/19/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
you can delete those files from the package ( MST)
Answered 06/19/2009 by: mekaywe
Brown Belt

Please log in to comment
0
Rob,

A *very* cursory glance (I do have work to do!) and run through the install and uninstall would suggest that running the very last CA in the EI sequence (DDSE_CA_Uninstall_CleanupDDSEDir_x86) removes those files. Try adding it in your MST and see what happens.
Answered 06/19/2009 by: VBScab
Red Belt

Please log in to comment
0
Thanks for the replies.. it's not a custom action that installs / removes these Ian as they are written via the File table.

mekaywe - certainly I can remove them in the MST.. but if they are not required - why are they even written..?! what a cr@ppy installer.... I don't know why I'm surprised - MS usually deliver the worst MSIs for enterprise deployments.
Answered 06/19/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Those files are related to License Agreement, Language Dlls which are required during UI installation.

These are not not at all deployed to target system and so can be deleted from file table in MST
Answered 06/19/2009 by: mekaywe
Brown Belt

Please log in to comment
0
I was looking to provide an installer for this product and found that if vcredist_x86.exe was extracted to the same folder - I would receive the disk cost error - more free space is required. So therefore, I specified another folder location and worked fine. I should have known as this is simular to an admin install (msiexec /a ). Just thought I would add this in...
Answered 12/08/2009 by: tron2ole
Third Degree Blue Belt

Please log in to comment
0
The solution here lies in the obvious and yet subtle realm of the base elements.

I speak, of course, of torches and pitchforks.

Lots of them.

In Redmond.
Answered 12/08/2009 by: Jsaylor
Second Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity