a release version asks for mfc42d.dll

i have a C++ Dll "A" that uses Dll "B".
i compile them both in release version.
but when i try to use them i am prompted that they can't
find mfc42d.dll / msvcrtd.dll .
how can i finf out why the debug libraries are linked instead of
the release versions.
i looked through the dsp files. but everything looks ok to me.

( Dll "A" is a inproc Com server )
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Maybe DLL "A" is loading the debug version of DLL "B". It may have a debug version in its current directory.
hedAuthor Commented:
yes i taught so as well + checked.
and at least the setting of dll "A" are pointing all right. since it's only a wrapping lib it's the same size of the debug version.
can i use some sort of pc elfdump?
Use the Depends utility to check it.
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

Sorry for that stupid question but...
Did you copy the release DLL to a place where right dll is found?
Normaly we all use for the first test of our program the debug DLL's to make the EXE running we most time copy the DLL to have access. Sometimes if we switch to release version the release DLL's are not copied or the are copied to a place later in DLL Search order.
My be you can check the localisation of the DLL's that are dynamically linked when the exe runs.
The easiest thing is to search for all occurances of the dll and then delete (or rename) all except the release version, to make sure it is being loaded.
Note: the dll loaded will be the one in the application's directory. If there is none there, then it will follow the normal Windows search method for DLL's (windows\system, path).
hedAuthor Commented:
the problem dissapeared. thank you vary much.
i think it was dll b that was a debug version.
most helpful was the depends tool remark because i didn't know this tool so ...
if chensu will publish some answer i"ll be glad to grant him the points. +
are there any other must know about tools that i"m missing ?
Thank you.

You may have a look at the Tools group that Visual C++ or Platform SDK install. There is a handy utility - Error Lookup, which is often ignored.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.