devxlogo

Debugger Isn’t Invoked

Debugger Isn’t Invoked

When working on developing or debugging an app created by automation (for example, by ActiveX DLL), if you normally invoke that app from a calling program (EXE), leave the calling program running and run the app you’re debugging in the VB Integrated Development Environment (IDE)-gotcha! Your debug and breakpoints won’t get hit. The calling program still has the “real” automation project in memory and isn’t using the version from the VB IDE. You must close down the calling program that’s running and restart it to use your VB IDE version. You’ll see an example of this when you try to make your automation project into a DLL and it balks, saying “Permission Denied.” You need to close down any calling programs.

See also  Small Business Strategies with Venmo
devxblackblue

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