ActiveX DLL, Debugging code when late binded.

[Devion]

Okay; Been a while since I've posted my own little dillema's.. Hopefully someone can point me in the right direction.

I'm building an application that's basically a base for late-binded DLL's that clients talk to.

Client --> Base --> Module(DLL)
The module responds and the Base just sends it back.

Anyway; Now the slight problem. It seems to be impossible to debug the code while being in the IDE (when working on the DLL. Waiting for the component to be created doesn't do anything at all. - I assume that it's waiting for it's GUID to be instanced?) - Is this a known problem and has someone solved this or am I now basically forced to log every action I do inside the module so if any problems occur I can track it via the log?

If the DLL hasn't been registered yet it's being registered on the spot (I'm thinking that this might be part of the problem and that the GUID's are mismatched at that point. Though it should only register if it can't find it.)

Oh before someone asks; I bind them by CreateObject, the data supplied comes from my script engine that's being parsed after initial start-up.

If anyone has any ideas or pointers feel free to reply =)

[Devion]

Mmh .. either not a lot of people are reading this dark part of the forum or no one has an idea? :/

[Dave Sell]

I have been able to live-debug everything I have ever worked on in VB6 except for a single case where I had a Singleton ActiveX control that used the ROT to set itself up as a Running Object.

In this case, the Object was known as VB6.exe and not its own executable name. If you are not doing this, then you should be able to debug any source code you have loaded in the IDE.