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
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)
Please log in to answer
Posted by:
brianb0177
15 years ago
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
Posted by:
mekaywe
15 years ago
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
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
15 years ago
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
15 years ago
As per my knowledge, nothing should be changed / modified in VendorMSI / MST.You're confused.
Could anyone provide me any standard document as a proof that we shouldn't touch MST created out of VendorMSI / VendorMSI itself.
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
15 years ago
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.