How DynaLog helps both you and us #302
CodingWonders
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In DISMTools 0.6, we introduced DynaLog, our in-house logging system. With DynaLog we can identify program issues more easily, even if we can't replicate them. These logs are in the
logsfolder of the application.DISMTools 0.7 introduced the log viewer (DynaViewer), which makes it easier to view the logs. Rather than staring at a notepad window, we can easily look at events in a cleaner way:
Initially, DynaViewer was going to be an internal tool, but we decided to include it later as a standard tool so it can also help you identify issues.
How DynaLog logging lets us understand program issues
During the development of version 0.6.1 we added DynaLog to the entire codebase. Based on that work, the log viewer lets you look at the exact events that happened before an error.
DynaLog and DynaViewer have been successful at helping diagnose issues and program exceptions in the past. For instance, they've helped diagnose an issue that would sometimes happen with the DISM API, that was eventually fixed in both the API and DT. They have also helped determine issues related to the console control used for DISM output redirection and STDOUT/STDERR encodings. When testing new features and fixes, we also rely on DynaLog when we don't use the debuggers.
These have been some examples of DynaLog and DynaViewer helping us. But, they can also help you.
How you can benefit from DynaLog logging
If, when performing an action, the program doesn't work correctly or throws an error, you can rely on DynaLog logs to help determine if it's an issue on your end or an actual software bug. You can access DynaLog logs via DynaViewer from the following locations:
DynaViewer.exein thetools\DynaViewerfolderOnce DynaViewer is launched, click the Browse button to open log files made by DynaLog. To learn more about an event, simply double-click it. Using DynaViewer can help you know what happened internally.
Of course, it's always nice for us to receive your logs. So, when reporting an issue of any kind, please send these!
DynaLog is no longer just used by DT
Ever since DynaLog was first implemented, more implementations have appeared:
In all implementations, DynaLog has been carefully implemented to prevent performance degradation.
This will let you report issues on both tools with the same level of detail.
Conclusion
DynaLog logging, and the log viewer, let you look at what the program does with more detail, in the event of an error.
If you have any questions or suggestions for DynaLog logging, don't hesitate to send your comments. When DynaLog is updated, the log viewer will also be updated.
Beta Was this translation helpful? Give feedback.
All reactions