Visual C++ 6.0 to Visual C++ .NET Conversion Problems

This article was previously published under Q321274
This article has been archived. It is offered "as is" and will no longer be updated.
When you convert projects from Visual C++ 6.0 to Visual C++ .NET, you may experience the following problems:
  • Additional include paths for Microsoft Interface Definition Language (MIDL) are not converted correctly. For example, the following statement may be lost in the converted .vcproj file:
    # ADD MTL /I "..\services					
  • By default, MIDL generates *.h files in Visual C++ 6.0 but generates *_h.h files in Microsoft Visual Studio .NET. If no header files are specified, Visual C++ 6.0 generates files that are named *.h.

    Additionally, the converted .vcproj file does not contain any header file names. However, if you open the converted .vcproj file with Visual Studio .NET, and if you look at the MIDL output setting, you see the following output:
  • A .dll file is generated instead of an .exe file. Although the original project may generate a Filename.exe file, the converted .vcproj file generates a Filename.dll file.
  • Preprocessor definitions that contain the string "UNICODE" or "_UNICODE" may be truncated. For example, if the original file contains a "CUSTOM_UNICODE" preprocessor definition, "CUSTOM_UNICODE" is converted to "CUSTOM" in the .vcproj file.
  • The .idl file exclusions may not persist across the conversion. For example, if two .idl files are excluded from the build with the following statement in the Sample.dsp file
    # PROP Exclude_From_Build 1						
    the conversion process may not generate the following equivalent statement in the .vcproj files:
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Visual Studio .NET service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date        Time      Version     Size    File Name                Platform   ---------------------------------------------------------------------------   13-Jun-2002 10:24:36  7.0.9508.0  364,544 VCProjectConversion.dll  i386				

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Article ID: 321274 - Last Review: 02/27/2014 21:12:49 - Revision: 1.3

Microsoft Visual C++ .NET 2002 Standard Edition, Microsoft Visual C++ 6.0 Service Pack 5

  • kbnosurvey kbarchive kbbug kbfix kbqfe kbvsnetpresp1fix kbhotfixserver KB321274