MSP handling
Hi!
I can't distribute MSPs seperately here (no post dependencies supported).
The only way to include them into a MSI is via administrative installation. I can't see the side effects, because I read some issues about updating/patching these installations. We never use them.
Applying them via the PATCH= property is only possible, if there are fixed paths to the MSPs. We don't have that, too.
Is there a way to run the MSP as a custom action?
Is there another way to merge MSI and MSP back to one MSI?
How do you handle MSPs?
cu Flo
I can't distribute MSPs seperately here (no post dependencies supported).
The only way to include them into a MSI is via administrative installation. I can't see the side effects, because I read some issues about updating/patching these installations. We never use them.
Applying them via the PATCH= property is only possible, if there are fixed paths to the MSPs. We don't have that, too.
Is there a way to run the MSP as a custom action?
Is there another way to merge MSI and MSP back to one MSI?
How do you handle MSPs?
cu Flo
0 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
