DLL Hell
From: bikerider7 (bay_bridge_tgv_at_yahoo.com)
Date: 07/23/04
- Next message: Gabest: "Re: enum handling change in VS 2005"
- Previous message: Mark Prenter: "Garbage Collection - Pointer out of scope, or not?"
- Next in thread: Ronald Laeremans [MSFT]: "Re: DLL Hell"
- Reply: Ronald Laeremans [MSFT]: "Re: DLL Hell"
- Reply: Sebastian Dau: "Re: DLL Hell"
- Messages sorted by: [ date ] [ thread ]
Date: 23 Jul 2004 11:45:58 -0700
Hello,
I have a .DLL compiled on VC++ 6.0 and is being linked into an
application built using 7.0. For reasons that are too stupid to go
into, migrating the .dll to 7.0 isn't possible for the time being.
On my development PC (Windows XP), the application runs fine; i.e.
the DLL calls work great. But when we copy the application over to
any other PC (also running Windows XP), it crashes whenever a DLL call
is made. It seems like calls to DLL library routines are going to a bad
address.
I've made sure that the .dll and .exe are in the same
directory, and we've run the app with the current directory set
to the app directory. I also went through to see if there were
any missing system DLL's on the other PC's but no such luck.
Is there something that I'm missing?
- Next message: Gabest: "Re: enum handling change in VS 2005"
- Previous message: Mark Prenter: "Garbage Collection - Pointer out of scope, or not?"
- Next in thread: Ronald Laeremans [MSFT]: "Re: DLL Hell"
- Reply: Ronald Laeremans [MSFT]: "Re: DLL Hell"
- Reply: Sebastian Dau: "Re: DLL Hell"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|