This article has been archived. It is offered "as is" and will no longer be updated.
If you run a release version of a Microsoft Visual C++ .NET 2003 Microsoft Foundation Class (MFC) application that was built in Microsoft Visual Studio .NET 2003 with optimization turned on, the MFC application quits silently. This behavior occurs when the OnDraw function is used to draw a zone.
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 2003 Service Pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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 usual 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 hotfix has the file attributes (or later file attributes) 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 ------------------------------------------------------ 04-Nov-2003 22:50 13.10.3308.0 1,867,776 C2.dll 04-Nov-2003 22:30 13.10.3308.0 86,016 Cl.exe
To work around this problem, turn off optimization of the OnDraw function by using the following code:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.