Debugging AIM plugins is always a challenge. If you are writing a plugin for Windows AIM clients that are C++, C# or VB or what we call native plugins, you simply attach the Visual Studio.net debugger (ctrl-alt-p) is the shortcut key combo, to AIM 6.8. Place your breakpoints in your project and you are all set to debug. For developers writing simple plugins using javascript like plugins via AIM Widget development, debugging requires breaking into JScript.
To be honest, this sucks if the all you are looking to do is peak into the way the Open AIM APIs work and maybe see why your plugin is not getting events. CoreWitness is just the plugin to make your life suck less. It gives you the ability to trigger specific events or dumps properties of objects in Open AIM.
The plugin was written in C++ and has the nice feature of self checking for updates, so as we add new objects or events to the Open AIM API, you will be the first to know. As I say, sometimes the best plugins are the utilities that let you see how we are doing things on AIM.
Hi Greg,
I just did as what you’ve said. I attached to the AIM, and set the breakpoint in C# code. However the breakpoint can’t be triggered at all. Any detail on how to set it?
Thank you very much.