Normally patch sequencing (and patch targeting) are done when building the MSPs
themselves by manipulating their applicability (targeting) and sequencing
(patchfamily) metadata.
In your MBA you can only control what users do using your bundle, you cannot
control what they do by using alternate
I worked on one product where verbose logging quadrupled the installation time
of the MSI over no logging at all, but in my experience that was an extreme
case (a few years ago).
If you want to isolate that as an issue (for test purposes) install the msi by
itself using the command-line genera
Any way it is workingI actually dont need to care about childs features
cause MSI will handle them
I just wanted to make sure same command line(ADDLOCAL and REMOVE) can be run
on both setup.exe
and MSI so we can test all our MSI in case something went wrong in the BA
After i will release BA
Hi Rob,
we've had this a while ago - pretty much all of your answers are being
marked as spam (in my Thunderbird installation with SpamAssassin as junk
filter).
If it helps - here's the (probably) relevant part of the plain message:
X-Spam-Score: 7.1 (+++)
X-Spam-Report: Spam Filtering perf
4 matches
Mail list logo
