After a time of more careful researching of logs I understand that error
occured in the install phase of major upgrade (Before that I thought that
error in the remove phase).
This means that I may avoid that error by setting more complex conditions
for remove actions. For example
Instead for exam
Hello, Phil. Thank you for answer.
But I don't clear understand.
/Q log shows " Product registered: entering
maintenance mode" and "Skipping FindRelatedProducts action: not run in
maintenance mode" which means that the product defined by the Q log
ProductCode must already be installed/
I thi
I don't think so.
I am testing on Virtual machine. First, I run test_setup_1, then do snapshot
and do major update on test_setup_2 in quiet mode.
After analyzing results I restore to the snapshot and do major update on
test_setup_2 with UI.
You wrote:
/but then you run the UI
install and that l
Hello, Phil.
Thank you for answer.
Here is the link to the source code and logs:
https://dropmefiles.com/3amOx
I have made simple minimal test project and same behavior occured.
In quiet mode:
MSI (s) (68:14) [00:37:40:531]: Feature: *Child1*; Installed: Absent;
Request: *Absent*; Action:
Hello.
I have installed product with some absent features.
Upgrading of product in quiet mode fails, because installer is trying to
remove absent features:
MSI (s) (1C:0C) [01:26:37:625]: Feature: AnyFeature; Installed: Absent;
Request: *Absent*; Action: *Absent*
But upgrading with UI
5 matches
Mail list logo
