/build/static/layout/Breadcrumb_cap_w.png

What Applications Should Not Be Repackaged?

What Applications Should Not Be Repackaged?


0 Comments   [ + ] Show comments

Answers (1)

Posted by: bkelly 20 years ago
Red Belt
3
Existing MSI packages should be deployed as they are. If customization is necessary, a Transform (MST) file should be used to introduce that customization. If you repackage an application and find that it references the MSI.DLL file, it is better not to repackage the application. Microsoft Office 2000 and XP are good examples.
Of course you can do it anyway- it is just not recommended. These applications are hard coded to use the Windows Installer service, and may make calls back to certain locations within the original MSI package.
Applications containing system files managed by the Windows File Protection features of Windows 2000 and later are also to be avoided, such as Internet Explorer, Windows Service Packs and certian hotfixes. For these a provided MSI or command line installation are your best bets.

Comments:
  • MSI command line - blink21 9 years ago
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