Shoutbox

is it possible to use the MessengerPlus_PluginChange command to unload the plugins from VB?

Ive tried, but with no luck.

It's for the installer for Screenshot Sender 3.


Cheers


Dempsey

just send the message to plus to reload the plugins via the VB SendMessage equivilent using the win32api or whatever - source code in the plus plugins api readme file

where is the reference to plus?

quote:

---

Originally posted by Dempsey
is it possible to use the MessengerPlus_PluginChange command to unload the plugins from VB?

---

Well, it should work, however I've had that problem too. It seems that plus doesn't unload VB plugins. I think that's due to the way they have to be loaded. The only way I know to delete a VB .dll plugin is closing messenger (and maybe plus too, I don't remember know).

its the messenger exe that locks the dll files, so you dont need to close plus!, only messenger

Can't you unregister them by using the win API? like regsrv32 does?

quote:

---

Originally posted by CookieRevised
Can't you unregister them by using the win API? like regsrv32 does?

---

Yes, you have to do that (regsrv32 /u <name>.dll), but messenger keeps it loaded in memory until you close it.

I have this problem too...Closing Messenger seems to be the only way...

May Patchou solve this?

quote:

---

Originally posted by Mnjul
I have this problem too...Closing Messenger seems to be the only way...

May Patchou solve this?

---

I don't think there's anything he can do. Although a DLL from Plus is who loads the VB DLL, that DLL (the one of Plus) is executed from the Messenger process, ie: from the view of Windows, it is Messenger who loads the VB DLL and, due to the special way the VB DLLs have to be loaded (because they aren't a "standar" DLL), that's why it isn't unloaded until Messenger ends.

I can be wrong (I'd wish) but I don't think so.

Yeah, the VB DLL loading procedure is fickle like that. I've found that VB itself can also register the DLLs: I used to build my plugins outside of the Plus! directory, but after finding out what VB does, I build them straight in the Plus! directory now.
To be fair, my experience with VB DLLs is limited, but what I have experienced has given me a valuable insight to how Windows works (or doesn't in some cases).