Re: deploy needs debug dll?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The problem with Depends is that it won't pick up anything loaded by LoadLibrary, so if
you have a debug DLL in the path that satisfies the request, it will load, and it will
then want the debug version of the C runtime. So Depends is not completely reliable for
this if there is any explicit dynamic linking going on.

You might try filemon or its successor to see when this attempt to load the debug DLL
occurs (by watching the trace, you'll see something load, which in turn loads something
else, etc., which loads the debug DLL)
joe

On Wed, 17 Oct 2007 05:31:06 GMT, Dan Bloomquist <public21@xxxxxxxxxxx> wrote:

Scott McPhillips [MVP] wrote:
"Dan Bloomquist" <public21@xxxxxxxxxxx> wrote in message
news:f%dRi.19136$ya1.8053@xxxxxxxxxxxxxxxx

I'm wondering if anyone has seen this.

First, several computers have a previous version of our deployment.
I've sent my executable and dlls out as pre release so some of my
clients could take the next version around the block and I could get
feedback. That works fine. And I've checked, I have not deployed a dll
called MSVCR71D.dll in that previous version.


Load up the Depends.exe tool and check each of your exe and dll modules
to find out which one needs MSVCR71D.

Yea, I've played with that in the past. I did, in the deployment folder
to be sure. Nothing. Everything is MSVCR71. I'll do a more extensive
search but now it will have to be after an intermediate deployment. We
have an appointment starting Thursday. But we have already planned to do
version 2.3.1.0 just cause we know how this goes. 2.3.0 will be just for
this trip, not the mailing. I want to avoid the patch thing as much as I
can, like it is the plague, it is so much work.

Thanks for the heads up, I forgot about depends.

Best, Dan.
Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.