You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I may have a patch that targets multiple Components A, B, and C and multiple Products Y and Z. It may be that Product MSI Z contains Components A and C while Product MSI Y contains Components B and C.
My Product may also have various baselines such as RTM and Service Pack 1. The current Pyro design makes it difficult to build such a patch. If a Binary in Component B changes, the patch should correctly update Product MSI Y but it will not because the .wixmst for Product MSI Z contains no changes.
This requires a huge amount of maintenance to continually update the patch definitions and know when Components have changes.
The feature request here is to allow Pyro, with a command-line parameter, to ignore the empty transform for Product Z in this case and simply patch Product Y. Later, when other changes are made to the Products, the patch will be able to pick them up and target both Product MSI Z and Y.
Originally opened by samuels
The text was updated successfully, but these errors were encountered:
Currently, I may have a patch that targets multiple Components A, B, and C and multiple Products Y and Z. It may be that Product MSI Z contains Components A and C while Product MSI Y contains Components B and C.
My Product may also have various baselines such as RTM and Service Pack 1. The current Pyro design makes it difficult to build such a patch. If a Binary in Component B changes, the patch should correctly update Product MSI Y but it will not because the .wixmst for Product MSI Z contains no changes.
This requires a huge amount of maintenance to continually update the patch definitions and know when Components have changes.
The feature request here is to allow Pyro, with a command-line parameter, to ignore the empty transform for Product Z in this case and simply patch Product Y. Later, when other changes are made to the Products, the patch will be able to pick them up and target both Product MSI Z and Y.
The text was updated successfully, but these errors were encountered: