add note regarding pch.h files#3963
Conversation
For a lot of us devs who generated MFC projects years ago, (re)generating new MFC projects create a pch.h header instead of a stdafx.h file. pch.h files include windows header files, but operate differently. This topic should be introduced and I can think of no better way than to address head on how to make CString compile. The Note I wrote needs to be formatted, for example, with green background.
|
@rtischer8277 : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Can you review the proposed changes? Note that the "Note" will have to be changed to the Docs-standard formatting for notes. IMPORTANT: When the changes are ready for publication, add a #label:"aq-pr-triaged" |
|
The following users don't have valid GitHub IDs, or are not collaborators on this repo: microsoftdocs/public-repo-pr-review-team |
|
#hold-off |
|
I think the pch.h CString Note and I am reporting here is a compiler bug and doesn't need a doc Note. CString is properly defined when generating an MFC project using the MFC App template, but not when generating a Dynamic-Link Library set to Using MFC.... I have indicated this change in Unable to compile with MFC CString using new pch.h. |
|
Thanks for logging the bug, @rtischer8277 |
For a lot of us devs who generated MFC projects years ago, (re)generating new MFC projects create a pch.h header instead of a stdafx.h file. pch.h files include windows header files, but operate differently. This topic should be introduced and I can think of no better way than to address head on how to make CString compile.
The Note I wrote needs to be formatted, for example, with green background.
By the way, I did submit feedback to the Developer Community about this, so maybe they will weigh in on the correct approach to all this. See Unable to compile with MFC CString using new pch.h.