I am working with unmanaged C++ DLL project, the DLL created is loaded into
an application (that I do not have the source) as an addin to the application.

In VS2005 both the release and debug versions of the DLL loaded fine (at
seperate times of course), but after converting the project to VS2008 only
the release version of the DLL loads, the debug version does not.

No other changes were made except for the conversion from VS2005 to VS2008.

Can someone help me fugure out why the debug version of the DLL will not load?

--
Harolds

Hi Harolds,

Can you provide more details regarding this issue? What exception do you
get during failure? What is the stack trace of the failure?

Also, how does the application loads your dll, statically linked or using
LoadLibrary? It would be helpful if you can provide a sample project to
reproduce this problem. If so, you may attach it a further reply using
Outlook Express.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

My guess is that the debug version of the CRT for Visual Studio 2008 is
missing. If you run dependencywalker on the Dll on the failing system it
should show you.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
"Harolds" <harolds (AT) nospam (DOT) nospam> wrote

dependencywalker shows the following:
Release Version:
MFC90.DLL could not find MSVCR90.DLL - though my.DLL shows it loaded
MSVCR90.DLL
MSVCP90.DLL could not find MSVCR90.DLL - though my.DLL show it loaded
MSVCR90.DLL

Debug Verion:
MFC90D.DLL could not find MSVCR90D.DLL - though my.DLL shows it loaded
MSVCR90D.DLL
MSVCP90D.DLL could not find MSVCR90D.DLL - though my.DLL show it loaded
MSVCR90D.DLL
my.DLL could not find MSVCR90.DLL

Why would it be trying to load a nondebug DLL?

--
Harolds


"Phil Wilson" wrote:

Please see my response to Phil Wilson's suggestion.

Thank you,
--
Harolds


""Jeffrey Tan[MSFT]"" wrote:

Hi Harolds,

Thanks for your feedback.

Do you mean that your dll statically linked with the MSVCR90.DLL but loader
and dependency walker can not find it? Since your dll statically linked
with the MSVCR90.DLL, have you tried to find out which function does your
dll import from MSVCR90.DLL? You may just use "dumpbin /imports" to examine
your dll imports API list and find the category for MSVCR90.DLL.

For testing purpose, I created a normal win32 GUI project in VS2008, but I
did not find any modules linked with MSVCR90.DLL yet.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

When I run C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\dumpbin.exe I
get "The application failed to start because mspdb80.dll was not found".

--
Harolds


""Jeffrey Tan[MSFT]"" wrote:

Hi Harolds,

Thanks for the feedback.

You should run dumpbin.exe from the VS2005 or VS2008 command
prompt(Microsoft Visual Studio 2005->Visual Studio Tools->Visual Studio
2005 Command Prompt) instead of normal cmd.exe. The VS2005 command prompt
contains more environment variable paths than normal cmd.exe. For example,
mspdb80.dll resides in "D:\Microsoft Visual Studio 8\Common7\IDE\". VS2005
command prompt can find it but cmd.exe can not find it.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support