Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

FYI: MFC BUG with Win2000 and Platform SDK

Posted on 2000-02-23
1
Medium Priority
?
603 Views
Last Modified: 2013-11-20
[Any comments on this from other Experts]

In order to access Win2000 specific APIs etc, one needs the following #define in the application's stdafx.h (before any other #includes)

     #define _WIN32_WINNT 0x0500

With the latest platform SDK, this also has the side effect of changing the definition for the OPENFILENAME struct; in particular it makes it larger.  This is because of the following lines in the "CommDlg.h"

     typedef struct tagOFNA {
        DWORD        lStructSize;
...
...
        LPCSTR       lpTemplateName;
     #ifdef _MAC
        LPEDITMENU   lpEditInfo;
        LPCSTR       lpstrPrompt;
     #endif
>>>  #if (_WIN32_WINNT >= 0x0500)
>>>     void *       pvReserved;
>>>     DWORD        dwReserved;
>>>     DWORD        FlagsEx;
>>>  #endif // (_WIN32_WINNT >= 0x0500)
     } OPENFILENAMEA, *LPOPENFILENAMEA;

This means when the definition of class CFileDialog is compiled, it's m_ofn member will have a different size than in the MFC dlls.  This is because CFileDialog is defined as:

     class CFileDialog : public CCommonDialog
     {
          DECLARE_DYNAMIC(CFileDialog)
     public:
     // Attributes
>>>       OPENFILENAME m_ofn; // open file parameter block
...
...
     };

When a CFileDialog is used in your code and is destructed, the wrong offsets into memory for member varialbes will be unsed, and in particular, the m_strFilter will not destruct properly.

The work-around for this is to #undef _WIN32_WINNT before the #include <afxext.h> in the application's stdafx.h:

>>>  #define _WIN32_WINNT 0x0500   /* allow Win2000 specific calls */
     #define VC_EXTRALEAN          // Exclude rarely-used stuff from Windows
headers
     #include <afxwin.h>         // MFC core and standard components
>>>  #undef _WIN32_WINNT           /* allow CFileDialog to build with the
correct size */
     #include <afxext.h>         // MFC extensions
     #include <afxdtctl.h>         // MFC support for Internet Explorer 4 Common
Controls
     #ifndef _AFX_NO_AFXCMN_SUPPORT
     #include <afxcmn.h>           // MFC support for Windows Common Controls
     #endif // _AFX_NO_AFXCMN_SUPPORT

Now, <afxext.h> will (indrectly) #include <CommDlg.h> and define CFileDIalog all without the offending _WIN32_WINNT.

NOTE: This only works because the VC_EXTRALEAN stops <afxwin.h> from including CommDlg.h earlier.

0
Comment
Question by:RONSLOW
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 3

Accepted Solution

by:
darinw earned 0 total points
ID: 2610632
Posting answer to save information to PAQ.

darinw
Customer Service
0

Featured Post

Moving data to the cloud? Find out if you’re ready

Before moving to the cloud, it is important to carefully define your db needs, plan for the migration & understand prod. environment. This wp explains how to define what you need from a cloud provider, plan for the migration & what putting a cloud solution into practice entails.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is to be the first in a series of articles demonstrating the development of a complete windows based application using the MFC classes.  I’ll try to keep each article focused on one (or a couple) of the tasks that one may meet.   Introductio…
Exception Handling is in the core of any application that is able to dignify its name. In this article, I'll guide you through the process of writing a DRY (Don't Repeat Yourself) Exception Handling mechanism, using Aspect Oriented Programming.
This video will show you how to get GIT to work in Eclipse.   It will walk you through how to install the EGit plugin in eclipse and how to checkout an existing repository.
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question