On Feb 11, 12:04*pm, Family Tree Mike
<FamilyTreeM...@discussions.microsoft.comwrote:
Quote:
Did you register (regsvr32) the com dll? *Is this a 3rd party dll? *Ifso,
which version is the later version?
>
>
>
"TC" wrote:
Quote:
I posted this question earlier, but didn't receive a reply, so I'm
going to rephrase it and try again.
>
Quote:
I have a VB.NET application which requires a COM DLL. When I add a
reference to the DLL, Visual Studio creates an Interop DLL. That seems
okay. I can compile the application and run it on my development
computer.
>
Quote:
When I copy the executable and all the DLLs over to the production
computer, however, the system does not use the COM DLL I put in the
application folder. It uses a different DLL which has a bug and causes
my application to fail.
>
Quote:
Why is the system using the wrong DLL? How do I force it to use the
right one?
>
Quote:
-TC- Hide quoted text -
>
- Show quoted text -
Kimiraikkonen and Mike,
Thank you for responding to my post. Here are details:
- Neither DLL is located in windows\system32.
- It is a 3rd party DLL. The buggy version is newer (1.3.4.333) than
the good version (1.3.1.247).
- The buggy version is registered. The good version is not. I'm afraid
to register the good version because I don't know what that will do to
the buggy version. This is the production computer, and other software
may rely on the buggy version.
-TC
