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
When trying to completely disable logging of a burn based bootstrapper using the Log Element
something strange happens. Instead of also disabling the logging that takes place in the MSIs,
log-files are created in the current-directory of the running bootstrapper executable.
The files created take the form:
(null)_0_MSI_PACKAGE_ID1.(null)
(null)1_MSI_PACKAGE_ID2.(null)
...
(null)[n]_MSI_PACKAGE_ID[n+1].(null)
I have created a temporary fix that involves changing the function LoggingSetPackageVariable
in logging.cpp. Checking the log-state to make sure logging is not disabled prior to creating
the logging filename used for the respective msis makes sure that no log is created if not
intended:
if ( BURN_LOGGING_STATE_DISABLED == pLog->state ) {
if ( psczLogPath ) {
*psczLogPath = NULL;
}
goto LExit;
}
Originally opened by info
The text was updated successfully, but these errors were encountered:
When trying to completely disable logging of a burn based bootstrapper using the Log Element
something strange happens. Instead of also disabling the logging that takes place in the MSIs,
log-files are created in the current-directory of the running bootstrapper executable.
The files created take the form:
(null)_0_MSI_PACKAGE_ID1.(null)
(null)1_MSI_PACKAGE_ID2.(null)
...
(null)[n]_MSI_PACKAGE_ID[n+1].(null)
I have created a temporary fix that involves changing the function LoggingSetPackageVariable
in logging.cpp. Checking the log-state to make sure logging is not disabled prior to creating
the logging filename used for the respective msis makes sure that no log is created if not
intended:
if ( BURN_LOGGING_STATE_DISABLED == pLog->state ) {
if ( psczLogPath ) {
*psczLogPath = NULL;
}
goto LExit;
}
The text was updated successfully, but these errors were encountered: