/build/static/layout/Breadcrumb_cap_w.png

Trying to setup an MSI from a custom application

I just started packaging software recently and was working on packagin an in house application we use. I wanted to setup an MSI because the users setup.exe is dropping dll's and ocx right into the system folder. My question is if I were to repackage this would the msi basically follow the same steps? Or would it isolate the dll's and ocx?
here are a list of the 6 files
asycfilt.dll
comdlg32.ocx
MSCOMCTL.OCX
MSHFlxGd.ocx
MSVCRT40.dll
vbar332.dll

The msvcrt40.dll is the one that caught my eye when the setup just dropped it in. I was going to also try to package using the installtion monitoring but figured it would fall along the same problems as before.

Any insight on how I could create an msi from his files?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: WiseUser 18 years ago
Fourth Degree Brown Belt
0
The files would still be copied to "System32" even if you isolated them.

Two of them are protected by Windows, and most (if not all) of them are part of existing Microsoft merge-modules.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ