Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
3Activity
0 of .
Results for:
No results containing your search query
P. 1
Packaging Best Practices

Packaging Best Practices

Ratings: (0)|Views: 109 |Likes:
Published by $!v@

More info:

Published by: $!v@ on Apr 07, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

03/19/2013

pdf

text

original

 
MSI Packaging Best Practices
1. Capture the application on Installshield template.2. Never use hardcoded paths in MSI/MST tables.3. Ensure that any junk value is not present in the registry table.4. Check for entries made by the application in Services and Host files (present insystem32\drivers\etc. folder)5. Any files going to User profiles should have an HKCU key as its key path.6. Any + in registry table can be changed to * ( this is not applicable for MM) Do this in.WSI file7. Component rules are to be checked. [HKCU + HKCR], [HKLM + HKCU], [HKCU + Files] insame component is not acceptable. Only exception here is for the component going to userprofile which will have [files + HKCU]. 8. [INSTALLDIR] property can be used for the installdir where ever possible instead of[PROGRAMFILESFOLDER]installdir9. Check for unnecessary launch conditions in vendor MSIs.10. Use MSI Table wherever possible. Avoid vbscripts/custom actions to the maximumextent.11. Kernel drivers are never captured by Wise. Always check for Kernel drivers for anyapplication, in the system registry/ in a Wise Install Manager or Master capture. Installthese kernel drivers using Service install table through theMSI(Refer \\16.138.16.101\KnowledgeDB\ ‘Client name’\Standards\HP Installing a KernelService.doc).12. Use Service Control table for starting and stopping services.13. Use HPTerminateProcess custom action for terminating processes.14. Use [!FileKey] in place of short paths to files in registry and inifile tables.15. Check for files/folders getting installed to Administrator’s user profile and removeAdministrator from directory table. Get the files / folders installed to all the users on aper user basis with the help of a HKCU registry key.16. Never hardcode inside a VBScript custom action. Use properties or environmentvariables.
 
MSI Packaging Best Practices
17. Use Date and Time properties where ever possible if application specific date or time ofinstall is captured.18. .hlp, .chm, .txt files installed to systemfolder need not be permanent. Just Share them.19. Files installed to System16Folder should be permanent.20. For transforms, do not move files/registry keys between components without checkingthe component conditions. Ensure that the integrity of component conditions are maintainedin the MST also.21. Have the file and its related registration information present in the same component.22. Add / Remove programs icon should be set as per the source. If source does not put anARP icon, set the main shortcut exe icon.23. Check for _Validation table errors in ICE validation24. .xla files [excel addins] should be placed in c:\program files\microsoft office\office10\library. If xla is in installdir then do not add the file to above location.25. In case of environment variable, If application is putting shortpath ie[c:\Progra~1\XXX~1\XXX.exe], retain the same in MSI.26. If Class table entries are present check for Warning / Errors in System Event Vieweronce you test the application functionality.27. Click all the executables in the applications in user mode and make sure they behave asper source in administrator mode.28. Click all the executables in the applications in before uninstall so that you are awareabout the processes that need to be killed.29. Check for MSI / MST repair in user mode. Make sure transforms created for vendorMSI repair correctly.30. It should be a clean uninstall. Any run time file created by the application should beremoved. Only user created and saved files can be retained.31. Make sure that dependency applications and your application work in Sync during yourapplication install. Make sure that dependency applications or the build applications are nottampered after uninstall.32. Using Installrite tool make sure that there are no deleted registry keys.33. After MSI uninstall, restart the machine and click on Search Option in Windows. Makesure it works as before.

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->