I'm apparently so ancient I am just looking at that line of code thinking "isn't that the standard entrypoint for a Windows app?", lol; is there something else to know? ;P Oh! I guess, staring at it, isn't that wrong?... if you use LPCTSTR, one would expect that you are trying to be agnostic to UNICODE, but then you also have to use _tWinMain, no? (And, after considering that, I went and double-checked, and the C is also incorrect in this context.)
Funnily enough, the "ANSI" versions of Win32 functions are no longer considered a legacy thing, now that the OS offers UTF-8 as the supported encoding, and apps can explicitly request it (regardless of non-Unicode codepage setting) via manifest:
