Reputation: 129
I have an issue that is only happening on one machine.
Here is the scenario. I have an EXE that is currently still developed in VB6, but I successfully migrated it's DLL to .NET. The EXE houses an object reference to a class in the DLL, and during startup initializes the object with the referenced DLL.
For some reason only on one machine it is unable to initialize the object, even though the DLL is properly registered (using ragasm.exe). All other machines do not have a problem.
The machine with the problem is a Windows XP 32-bit computer, and the user is logged in as an admin. I have even manually registered the DLL, with no problems, but the program still cannot create the reference to it.
Not sure what other steps I could take to debug this problem. Logically it should be working since it is registered properly.
Thanks, Chris
Upvotes: 0
Views: 343
Reputation: 10855
Use process monitor to see where your app goes off track.
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
You should see the VB6 app hit the registry to find the location of the DLL, and then see it access the filesystem to locate the DLL. Post back with results if you are still stuck after that.
Upvotes: 1