From what I remember at the old times starting development of Windows applications, TEXT macros would be placed around strings to locate the strings which you want the compilation to differ where it should be considered a Unicode String or a MBCS (MultiByte Character sets)… Nowadays it is a sort of legacy method, since there is no real reason on the target platforms to not use Unicode, so if you want to keep your code consistent you should still use it, because mainly we never know when a macro would change and future changes on string standards would clearly target the TEXT macro to have its content change to accomodate the changes.