Phil Jollans
01-30-2002, 08:26 AM
I have added a nested install to my install package.
Following the advise found in newsgroups, I have added the custom action twice - with appropriate conditions - once to install it and once to remove it.
I am using custom action type 7, so that the nested MSI package is stored inside my install package.
Judging by the size of the resultant package, it has been included in the package twice. Since the nested package is about 28 MB, this is significant.
Can anybody confirm this behaviour and does anybody know a way to stop it?
On idea would be to pass pass in the Remove parameter with the syntax REMOVE=[REMOVE], in which case I would not need to have two custom actions. Does anyone know if that would work?
Thanks
Phil
Following the advise found in newsgroups, I have added the custom action twice - with appropriate conditions - once to install it and once to remove it.
I am using custom action type 7, so that the nested MSI package is stored inside my install package.
Judging by the size of the resultant package, it has been included in the package twice. Since the nested package is about 28 MB, this is significant.
Can anybody confirm this behaviour and does anybody know a way to stop it?
On idea would be to pass pass in the Remove parameter with the syntax REMOVE=[REMOVE], in which case I would not need to have two custom actions. Does anyone know if that would work?
Thanks
Phil