Deploying a DLL

Hot Topic

Rebuild using shared precompiled headers doesn't work
On adjacent ">"s in a parameterized declaration
Including resources in EXE?
Performance for C code
passing commandline arguments to an external exe
WM_KEYDOWN
timer is not panctual
rand()'s initial value seems very non-random
Handles on a 64 bit OS
C# to C++

Visual C++

how to determine if an open file is NUL: or not
error LNK2001: unresolved external symbol "void * __cdecl operator new(unsigned int)"
im a beginner/ need help
'm_hWndLastControl' : is not a member of 'CDataExchange'
Type Conversion from _varaiant_t to CByetArray
creating exe's and running them
Owner drawn list box(Problem in comparison)
Multithread and Visual C++
Disconnect keeps the Remote XP session for a minute. How to logoff?
Invalid signal

Deploying a DLL

Greetings,

I have a DLL that gets loaded from (my) javascript subsystem that executes within the environment of a major, industry stanard, trading application. The DLL was developed using C++ and VS2005. The DLL does NOT use the Common Language Runtime. It uses MSMQ via importing:

#import "mqoa.dll" no_namespace

The good news is that the DLL works perfectly, on my system. The bad news is that if I send it to a client, it aborts with an error from the trading application saying that the 'dll cannot be found.' I sent the DLL to other clients as well as the support group of the company that makes the industry standard trading application. Same result. The client systems had MSMQ installed and the .NET Runtime as well. And I should mention that I triple checked with each client to ensure that the DLL was in the right place.

Can anyone advise me what I have neglected to do in sending this (simple) DLL to my clients

Tx,

Scott




Answer this question

Deploying a DLL

  • Sonmez

    Might even be an SxS issue. Search this forum for threads on SxS.

    Scott Masters wrote:

    I checked and all client systems are running same service packs I am running (up to date) and mqoa.dll is on their system in the windows/system32 directory.

    Scott



  • jatwood

    The only thing I can think of is that the DLL has been placed somewhere that it can't be found. The two best directories to put them are either the application directory or system32. Anywhere else and it would need to be a directory in the path.



  • Alexander Klizhentas

    Are you sure it's mqoa.dll that's not being found You can check if that's the case with Dependency walker. Make use of its profiling feature (Profile -> Start Profiling). You need to profile the trading application (the exe) instead of your DLL.

  • ChrisRichardson

    Oshah...many thanks. Used Dependency Walker with profiling. Client did not have the VC++ runtime. I sure felt stupid for not thinking of that in advance....Scott

  • Peter Poirier

    I checked and all client systems are running same service packs I am running (up to date) and mqoa.dll is on their system in the windows/system32 directory.

    Scott



  • Moussa El-tayeb

    Are there any differences in the OS version or service packs   Can you locate the mqoa.dll on the users machine

  • Deploying a DLL
Answer this question