Re: Passing parameters to a Com DLL
"WishfulDoctor" <WishfulDoctor@discussions.microsoft.com> wrote in
message news:60BDED0A-82B9-4B81-9B68-CC956D984EDB@microsoft.com
I am still having problems getting the 'break' during debugging. I
have built the dll in debug mode and it is registered. I have set
the 'command' in Properties/Debug to be the full path of the VB .exe
file. I have set breakpoints in the method being called. When I
press f5, the vb program is started - I fill the data and click the
button to call my dll - it is called and value returned to the VB
program without stopping at the breakpoint. What am I missing?
The DLL that's registered is not the same one you want to debug. Check
the path in the registry under HKCR\CLSID\{Your CLSID}\InProcServer32.
Alternatively, once you are debugging, check the Modules window (Debug |
Windows | Modules) and see where your DLL is being loaded from. You'll
likely find that a different copy is being loaded, e.g. a release build.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925