Well, that's right. Thank you for your reply. Really my situation is a bit more complex, but trying to find the issue in my tests I made some mistakes.
So this is the situation which I cannot find a solution for.
I have an installer A, which has various prerequisites and a chained package B, which has another chained package C.
B and C are the ones of my previous example, with the complex evaluation condition.
The property MYVAR is read correctly from the .ini file, as I can see it's value in the logs.
Anyway there is no way to install package C.
Package A has external resources.
Package B is an msi with resources inside. The only unusual thing is that package B is not registered with Windows Installer.
Package B starts everytime, but noway to start installation of package C
This is an extract of the logs regarding C package
MSI (s) (34!1C) [18:31:37:227]: PROPERTY CHANGE: Adding AI_CHAINER_CMD_LINE property. Its value is 'IC:\Users\QServer\AppData\Local\Temp\Apetta.msiFV'.
MSI (s) (34!1C) [18:31:37:227]: PROPERTY CHANGE: Adding AI_MSI_CHAINER_CONDITION property. Its value is '1'.
MSI (s) (34!1C) [18:31:37:227]: PROPERTY CHANGE: Adding AI_CommitChainers property. Its value is 'C:\Users\QServer\AppData\Local\Temp\Apetta.msi'.
MSI (s) (34!1C) [18:31:37:227]: Doing action: AI_CommitChainers
Inizio azione 18:31:37: AI_CommitChainers.
MSI (c) (A0:54) [18:31:37:227]: Creating MSIHANDLE (3270) of type 790531 for thread 7764
MSI (c) (A0:54) [18:31:37:227]: Closing MSIHANDLE (3270) of type 790531 for thread 7764
MSI (c) (A0:54) [18:31:37:227]: Creating MSIHANDLE (3271) of type 790531 for thread 7764
MSI (c) (A0:54) [18:31:37:227]: Closing MSIHANDLE (3271) of type 790531 for thread 7764
Termine azione 18:31:37: AI_CommitChainers. Valore di ritorno 1.
MSI (s) (34!1C) [18:31:37:227]: PROPERTY CHANGE: Deleting AI_CommitChainers property. Its current value is 'C:\Users\QServer\AppData\Local\Temp\Apetta.msi'.
MSI (s) (34!1C) [18:31:37:227]: Closing MSIHANDLE (6065) of type 790540 for thread 6172
MSI (s) (34!1C) [18:31:37:227]: Closing MSIHANDLE (6064) of type 790541 for thread 6172
MSI (s) (34!1C) [18:31:37:242]: Closing MSIHANDLE (6062) of type 790541 for thread 6172
MSI (s) (34:30) [18:31:37:242]: Closing MSIHANDLE (6061) of type 790542 for thread 836
Termine azione 18:31:37: AI_PrepareChainers. Valore di ritorno 1.
.
.
.
Property(S): AI_CHAINER_CMD_LINE = IC:\Users\QServer\AppData\Local\Temp\Apetta.msiFV
Property(S): AI_MSI_CHAINER_CONDITION = 1
No error. Windows Event Viewer has no evidence that apetta.msi has been launched.
Btw: package B has verbose logging enabled. I don't know why, and I'm not able to reduce it. Where do I setup logging parameters for a chained package?
Catalin wrote: ↑Thu May 21, 2020 3:46 pm
And I think there is no way to test the presence of a value in an INI file, so that I could create 3 variables MYVAR_A, MYVAR_B, MYVAR_A_B
Actually, there is. You can check if a value is present in an INI file by using an
"INI File Search".
This is not clear to me. It seems not to be what I was asking for: I can check the presence of a key of any value, but I cannot specify the presence of a specific value for the key. I meam: I can search for section S, key K and obtain its value "VV" or "XX", but I cannot test if the key K has value "XX" (so that the variable is true or false)