Best of all, it will add runtime CallStack capabilities to your applications. From now on, if an error occurs at runtime, you won’t have to guess what happened :-)

Download it here

Short Description:

After installation, the add-in will load on startup of Visual Basic. A new toolbar will be available. Button functions starting from the left:Add error handling code to the current procedure, add error handling code to the current module, plug-in options.

Depending on the option settings, the plug-in might add multiple files to your project. The source code to those files is in SRC directory of the plug-in. Feel free to customize it at will.

Screenshots:

Standard error message

Detailed error message,
includes the callstack

Plug-in options

This sample will teach you how to expose classes from an ActiveX EXE to other Applications. I felt that a Main App / Plugin relationship (like in Photoshop) will be best suited to showcase this cool solution.

This is how it works:
When an object gets created based on a class from an ActiveX Exe it gets created in its own memory area (Multiple objects based on the same class cannot share their data). In C++ that object registers itself with the ROT (Running Object Table) so that anybody who needs to, can access that instance of the object. For instance Excel. When Excel is running you can refer to the running instance from VBA/VB, and access any data that’s present in the spread sheet. However VB based objects lack that functionality. Activex EXE created in VB will NOT get registered in the ROT! (That’s why you can’t use GetObject on VB made ActiveX’s ;-) )

Anyhow, here is a solution that will register your ActiveX EXE in the ROT, and you will be able to reference the running instance of your object from any other application.

Please use this sample as follows:

1. Extract Files from Zip (use folder names checked)
2. run MainApp.EXE (ActiveX EXE)
3. click on the OPEN icon
4. load the supplied BMP
5. wait for a few sec….(sorry the image handling is awfully slow, I didn’t wanted to deal with DIB’s for simplicity reasons)
6. plugin Button should be enabled by now (this calls a ShellExecute and runs a regular EXE (our plugin)
7. In the plugin click on GetData (this will transfer the image from the main app)
8. click on modify image
9. click on Close Plugin & Transfer data (this will transfer the modified image back to the main app)
10. Voila

The benefits: If you expose your app’s objects up front, you can later on create any plugins/addons you want without modifying the original app.