为什么MFC .rc文件有时有时在末尾手动插入\\ 0？

Question

Within this article , I notice that \\0 is inserted into the #define statements for building version strings. I've also seen it in some MFC projects that I am maintaining. While going through the process of moving version resources into a .rc2 file where I can use one header include to setup the versions across all of my projects I've noticed the \\0. In some cases it causes no problems, but in some cases the properties window of the resulting compiled file will show a trailing quote ("). Removing the \\0 doesn't seem to hurt anything, but I don't understand why they would ever be needed. Hopefully there are some old school MFC gurus that understand this that can explain whether removing the \\0 is recommended or not.

Example:

    VALUE "FileVersion", VERSION_STR"\0" // <-- adding it here causes the version to show in the properties dialog as 1, 0, 4, 1" which is odd.  
    VALUE "InternalName", "DaHelper\0" // <-- what is the \0 for? Isn't it already a string literal null terminated without adding \0?

Answer 1

May be nobody has a real answer for it.

Also the documentation shows no rule for it. The samples in the MSDN (your link) show the same defines, when using strings. Only a few are shown. But I rechecked real old sources sind 16bit times. It was always the same. The VALUE types are all terminated by a \\0 character. Seams that the string defines in the resource editor for this type of resource is not automatically \\0 terminated.