Debugger is not Being Invoked

Debugger is not Being Invoked

When working on developing or debugging an app that is created via automation (i.e. ActiveX DLL), keep in mind the following: if you invoke that app from a calling program (exe) in a normal fashion and leave the calling program running, then run the app you are debugging in the VB IDE, GOTCHA!, your debug and break points are not going to get hit. The calling program still has the “real” automation project in memory, and is not using the version from the VB IDE. In order for your VB IDE version to be used, you must close down the calling program that is running and restart it. You will also see an example of this when you try to make your automation project into a DLL and it balks, saying “Permission Denied.” Again, close down any calling programs.

See also  11 Effective Keyword Research Tools and Techniques

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist