RE: Assertion in afxwin.inl line 24.

Dear JLD,
There are a couple of ways to turn of the throwing of assertions, some of
them most newsgroup members would think is disgusting, and others may approve
of. The way that I use to turn off assertions is to set my MFC project to
Release mode. In Visual C++, setting a project to Release mode disables all
of the macros in code (both yours and Microsoft) that perform safety checks
upon your code (such as throwing that assertion). There is likely some
reason why the assertion was called, and it was likely your fault, however
setting the project to release mode could very likely turn off this assertion.

Here is something else to think about:
What happens when you statically link MFC libraries?
You mentioned that the assertion is not thrown if you use the shared model
of linking MFC in versus statically linking MFC. It seems to me that this is
likely at the root of the problem, as you have mentioned. Sometimes even the
best linkers can miscalculate what components of the MFC libraries you "need"
inside of your exe, and can omit something that can later cause an assertion
to be thrown! There is something which your application needs in MFC, that
linker cannot figure out! Use as shared library likely fixes this error
because when your app runs with this, Windows can pick and choose whatever
libraries it needs. A couple things to look at include seeing if the
controls/componenets you are using require an additional .lib file to be
included in at link time (some do infact require that if you must use static
linking). Another helpful thin to do is to build the app using shared MFC
libraries and then run Depends, an app that comes with Visual Studio, on your
program. This application will tell you what DLLs you are using as you run
your app. If you check online, you will find out how to use the Depends app
if you don't know how to. The full name of the app from Microsoft is
Dependency Walker. By knowing what DLLs you app uses, you can quickly find
out where the linker is failing! This is the theory that your app is failing
becacuse the linker is omitting key libraries.

Regards,

James Simpson
Straightway Technologies Inc.
"ggurubasavaraja@gmail.com" wrote: