BUG: AppWizard Project Cannot Open Include File .RC2

Last reviewed: July 31, 1997
Article ID: Q170530
The information in this article applies to:
  • The AppWizard included with: - Microsoft Visual C++, 32-bit Editions, version 5.0

SYMPTOMS

When you build an AppWizard-generated project, the resource compiler reports the following error if the default code page is anything other than 1252 (for example, you have an Eastern European or Asian system locale):

   <project\project.rc>(118) : fatal error RC1015: cannot open include file
   'res\\XXXXXXX.rc2'.

This error only occurs when the project name contains characters greater than 0x7F hex.

CAUSE

The Resource Script for the project that AppWizard generates is hard-coded to specify the code page as 1252 and the language as US English. When the Resource Compiler attempts to load an RC2 file with a name that has characters greater than 0x7F hex, but the code page 1252 has been specified, the Resource Compiler will not be able to open the RC2 file.

RESOLUTION

To work around this problem, do the following in the project's .RC file:

  • Replace all references to code_page(1252) with the proper code_page.
  • Replace all references to "Language 9,1" with the proper language, sub-language code pair.

There are three places in a typical RC file to change these values:

  1. In the TEXTINCLUDE section, TEXTINCLUDE 3 has a reference to the code_page and Language:

          3 TEXTINCLUDE DISCARDABLE
          BEGIN
    
              "#define _AFX_NO_SPLITTER_RESOURCES\r\n"
              "#define _AFX_NO_OLE_RESOURCES\r\n"
              "#define _AFX_NO_TRACKER_RESOURCES\r\n"
              "#define _AFX_NO_PROPERTY_RESOURCES\r\n"
             "\r\n"
             "#if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENU)\r\n"
             "#ifdef _WIN32\r\n"
             "LANGUAGE 9, 1\r\n"
             "#pragma code_page(1252)\r\n"
             "#endif\r\n"
             "#include ""res\\appwizdll.rc2"" // Non-Microsoft Visual C++
                                              // edited.
                  "\r\n"
             "#include ""afxres.rc""    // Standard components\r\n"
             "#endif"
              "\0"
          END
    
    

  2. Immediately after the TEXTINCLUDE section, a set of preprocessor definitions has a reference to the code_page and Language:

          #if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENU)
          #ifdef _WIN32
          LANGUAGE 9, 1
          #pragma code_page(1252)
          #endif
    

  3. At the end of the .RC file, there is a last set of preprocessor definitions with a reference to the code_page and Language:

          #if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENU)
          #ifdef _WIN32
          LANGUAGE 9, 1
          #pragma code_page(1252)
          #endif
          #include "res\\appwizdll.rc2"  // Non-Microsoft Visual C++ edited
    
                                         // resources.
          #include "afxres.rc"    // Standard components
          #endif
    
    
To make these changes, open the project's .RC file clicking Open on the File menu and selecting an Open As type of "Text" instead of "Auto." Visual C++ will close the resource editor if it is open for this project.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords          : vcbuglist500 WizardIss kbtool
Version           : 5.0
Platform          : NT WINDOWS
Issue type        : kbbug


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 31, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.