DOC: Documentation Errors in Technical Note #33

ID: Q99576

The information in this article applies to:

SUMMARY

Instructions on linking an application with and using the Microsoft Foundation Classes dynamic-link library (DLL), MFC200.DLL, are provided in Technical Note #33. To access this Technical Note, use the MFC Tech Notes help file in the Microsoft Visual C++ program group. Technical Note #33 deals with implementation and usage issues regarding this, and other DLLs. However, this Technical Note contains three errors that might cause some confusion.


MORE INFORMATION

The first error is in the "Overview of MFC200.DLL support: Terminology and Files" topic. Under the sub-topic "_USRDLL," the following appears: 


   In MFC 2.0 we support user DLLs with all the new MFC 2.0
   functionality including OLE support but no including VBX support.
This should read: 

   ..."including OLE support but not including VBX support."
The second error is in the "How to write an MFC extension DLL." Under the sub-topic "LibMain," the following appears: 

   You can add addition one-time initialization here if you are
   careful not to allocate memory.
This should read: 

   "You can add additional one-time..."
The third error is also in the "How to write an MFC extension DLL. Under the sub-topic "CWinApp vs. CDynLinkLibrary," the following appears: 

   As well will see later, the MFC200[D].DLL stored per- application
   data in a special part of the client application's stack segment.
This should read: 

   "As we will see later..."
The first documentation error was fixed, but the second and third still remain in the Visual C++ 1.5.

Additional query words: 1.00 1.50 2.00 2.50 


Keywords          : kbdocerr kb16bitonly kbMFC kbVC100 kbVC150 
Version           : 
Platform          : 
Issue type        :

Last Reviewed: August 8, 1999