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
As a WiX Developer, I want to have .NET Trace Logging capability that provides logging useful for debugging and diagnosing run time issues with the WiX tool chain so that I can more effectively diagnose and resolve run time bugs in the WiX tool chain.
This tracing would be off by default. .NET Tracing is enabled when either DEBUG or TRACE are defined for the build. Some decision will need to be made whether the tool chain would deploy with the ability to trace in the field, or whether a DEBUG or TRACE version of the tool chain would be needed for tracing.
Also, the information desired for logging and its format would need to be ironed out. I have some initial ideas which will be in a forth-coming WIP.
This development can be done in parallel for both WiX3.x and WiX4.x.
Originally opened by jmcooper8654
The text was updated successfully, but these errors were encountered:
As a WiX Developer, I want to have .NET Trace Logging capability that provides logging useful for debugging and diagnosing run time issues with the WiX tool chain so that I can more effectively diagnose and resolve run time bugs in the WiX tool chain.
This tracing would be off by default. .NET Tracing is enabled when either DEBUG or TRACE are defined for the build. Some decision will need to be made whether the tool chain would deploy with the ability to trace in the field, or whether a DEBUG or TRACE version of the tool chain would be needed for tracing.
Also, the information desired for logging and its format would need to be ironed out. I have some initial ideas which will be in a forth-coming WIP.
This development can be done in parallel for both WiX3.x and WiX4.x.
The text was updated successfully, but these errors were encountered: