I notice that in 6.0.x.x, if the design includes an installation log, the log is not created if the setup is aborted. Is this intentional? If so, what is the reasoning behind it? It seems to me that one important reason for the log feature is diagnosis. One thing that I need to diagnose is when a condition causes the setup to abort, but the condition for aborting was not intended to be met in the circumstances of that install. Not having a log for an aborted setup makes the diagnostic process less convenient.
Announcement
Collapse
No announcement yet.
no log if aborted
Collapse