/build/static/layout/Breadcrumb_cap_w.png

Vendor MSI _ Please Reply

Hi,

I am working on a VendorMSI and would like to know if we can edit the tables in MST created out of the VendorMSI.

Can we modify components / merge modules / files / registries and comment custom actions present in MST created out of VendorMSI

Can we set keypath for components which doesn't have by default to support self-healing of the application.

Could anyone let me know where we can find the global standards documented for application packaging

0 Comments   [ + ] Show comments

Answers (5)

Posted by: brianb0177 11 years ago
Senior Yellow Belt
0
ORIGINAL: mekaywe

Hi,

I am working on a VendorMSI and would like to know if we can edit the tables in MST created out of the VendorMSI.


Yes you can within the MST as you are not editing the tables of the vendor MSI.

For Best Practices see http://msdn.microsoft.com/en-us/library/bb204770.aspx and http://itninja.com/blog/view/appdeploy.com->-training-videos->-repackaging-best-practices
Posted by: mekaywe 11 years ago
Brown Belt
0
so can we play with tables / components / merge modules present in MST created out of VendorMSI?

As per my knowledge, nothing should be changed / modified in VendorMSI / MST.

Could anyone provide me any standard document as a proof that we shouldn't touch MST created out of VendorMSI / VendorMSI itself.

Regards
RaviKiran
Posted by: brianb0177 11 years ago
Senior Yellow Belt
0
ORIGINAL: mekaywe

so can we play with tables / components / merge modules present in MST created out of VendorMSI?

As per my knowledge, nothing should be changed / modified in VendorMSI / MST.

Could anyone provide me any standard document as a proof that we shouldn't touch MST created out of VendorMSI / VendorMSI itself.

Regards
RaviKiran




That is correct, modifying the MST does not change the vendor's original MSI.
Posted by: anonymous_9363 11 years ago
Red Belt
0
As per my knowledge, nothing should be changed / modified in VendorMSI / MST.

Could anyone provide me any standard document as a proof that we shouldn't touch MST created out of VendorMSI / VendorMSI itself.
You're confused.

You're right in supposing that you should not edit vendor-supplied MSIs. You use transform files (MSTs) to effect changes to the MSI. An MST is a delta on the original database (MSI). You can think of it as kind of an incremental back-up of the MSI, in that it contains any changes you require to the original MSI but without touching the MSI.

Is that any clearer? :)
Posted by: MSIPackager 11 years ago
3rd Degree Black Belt
0
Could anyone let me know where we can find the global standards documented for application packaging

haha that's funny.
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