hex 0x07 redux
Yesterday I made the comment that I thought that the handling of 0x07 was a bug in the TFS client APIs.
I was wrong.
Buck called me out on this and after researching it in more depth I believe that the client OM is doing the right thing (or at least the best thing it can do).
The offending application is the one that is causing fancy quotes to be crushed down to 0x07 instead of the proper Unicode value (0x07 is one of the bytes in the multi-byte stream – the other bytes form other noise characters that happen to be valid in XML). In my specific case the version control system I was reading the source data from was causing this to happen.
You can read an MSDN Q/A about this issue here: