Improvements in TRACE for Wire Protocol

[josesimoes]

Description

• Define single method used to TRACE WP headers and replace the copy-paste with single macro to call the method and ensure uniform traced output when debugging WP message exchanges.
• Remove TRACE calls from debugger class.

Motivation and Context

• Uniform trace data that matches data traced by Debugger on PC. Additional data formatting in a way that is easier to read.
• On debugger class the TRACE usage wasn't bringing much value.

How Has This Been Tested?

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (work on Unit Tests, has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[nfbot]

Hi @josesimoes,

I'm nanoFramework bot.
Thank you for your contribution!

A human will be reviewing it shortly. 😉