Article ID: 839287 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows Registry
If you want the Visual C++ editor to treat files as Visual C++ files, you must specify the file name extensions in the NCB Default C/C++ Extensions key in Microsoft Visual Studio 2005, in Microsoft Visual Studio .NET 2003, and in Microsoft Visual Studio .NET 2002. When the editor treats the files as Visual C++ files, the files are colorized, and Microsoft IntelliSense is established on the files. The following is the registry key that contains these values:
For a file type to be treated as a Microsoft Interface Definition Language (IDL) file, the file name extension must be specified in the NCB Default IDL Extensions key. The following is the registry key that contains these values:
The following is an example of the values that this registry key typically holds:
NCB Default C/C++ Extensions=".cpp;.cxx;.c;.cc;.h;.hh;.hxx;.hpp;.inl;.tlh;.tli;"
NCB Default IDL Extensions=".odl;.idl;.odh"
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
If you want the Visual C++ editor to treat a file type as a Visual C++ file, modify the value of the NCB Default C/C++ Extensions key. If you want a file type to be treated as an IDL file, modify the value of the NCB Default IDL Extensions key.
To modify the registry, follow these steps:
For additional information, visit the following Microsoft Developer Network (MSDN) Web site:
Article ID: 839287 - Last Review: January 17, 2015 - Revision: 3.2