I realized that the ATLASSERT macros in my APOs were not generating anything, even in the Checked build environment (Vista x86). I looked into it, and it appears that defining _DEBUG for crtdbg.h is the immediate switch for generating the significant code for debug builds. However, when I defined _DEBUG at the top of e.g. spkrfillapo.cpp (the speaker fill sample code) I get compilation errors (AE_IS_VALID_TYPED_READ_POINTER not defined).
Is there a special requirement for enabling ATLASSERT within an APO checked build? Has it been intentionally left disabled? Possibly I've damaged my build environment somehow.
Bill ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/