I found out what was causing the compile error. The problem occurs because I was using the default demo CMAKETEXT.txt file as supplied by Graphisoft to generate the VS build file.
I created a custom AddOn using snippets from the example files. One included: const GS::UniString which is a wchar_t. VS now treats that as a built-in function, Archicad, however, defines it as a typedef -- the old method.
There is a compiler switch to switch between the two but ON is the default. Graphisoft's Cmake does not include this option so by default, it is ON, which will result in a compile error if UniStrings are used within. The solution was to simply change the property switch to NO which will use the typedef.
Others may come across this problem in the future if you use Cmake. The NO option should be included in the Cmake txt file but might then cause other problems. This brings to mind that other compiler switches may be needed for other snippets of code. This should be defined in the examples.
Since Graphisoft may be moving, in the future, to use Cmake in their examples, they should recognize that it will make it easier to cut/paste from the examples but then compiler switch settings may be affected depending on what code is being reused.
I don't have a solution other than to suggest that more documentation from Graphisoft regarding Cmake's options be included in the demo files. Assuming that Graphisioft decides to use it.
Cmake can be very complicated, but as I see it, most of the commands/options are repeated in groups and are readily understandable once explained and only a few are used.
Hope this helps someone who may also come across this in the future.
Thank you for pointing this out. We constantly try to make the compilation as close to Archicad's own compilation as possible. I've already known about this one, but it didn't cause any errors in Add-Ons before.