/build/static/layout/Breadcrumb_cap_w.png

What to choose for MSI Key path?

In my application one of my component has exe, dll and ocx. What I have to set as keypath?


0 Comments   [ + ] Show comments

Answers (4)

Posted by: pjgeutjens 11 years ago
Red Belt
3

one component should only contain one exe, dll or ocx, so give each of these files their own component and make them the keypaths of each.

Posted by: piyushnasa 11 years ago
Red Belt
2

Is it a vendor MSI or have you captured it.

If it is a Vendor MSI, do not change anything. If it is yours then create separate component for each and set each as keypath.

For Vendor MSI, if you have these 3, you can choose any but I would have gone with exe.


Comments:
  • if it's a vendor MSI, also call the vendor and offer to teach them the basics of MSI packaging... - pjgeutjens 11 years ago
  • Personally I have no problem editing/correcting vendor msi so that they function properly (in your environment). Though better understanding of features/components/key paths/repair/self-healing is definitely suggested before doing so. Obviously using best practice methods via mst instead of direct edits. - dandirk 11 years ago
Posted by: jagadeish 11 years ago
Red Belt
1

Is it true?

Posted by: dandirk 11 years ago
Third Degree Green Belt
1

Pjpeutjens and piyushnasa are right on, but there is more.

Keypaths/files and how msi uses them is critical to packaging, especially handling per user data with a per computer installation.

Understanding msi repair/self-healing are VERY important concepts, keypaths/files are central to their proper use and functionality.

Excellent itninja thread on self-repair... http://www.itninja.com/question/self-heal-for-install-shield-msi#24172

Look at jmcfadyen's posts

 
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