If you want to build an installer for your plugin, the following info may be useful.
Though i think it would be even more useful if we wrote a generic installer for plugins and added a way for FARR itself to guide user through installing a plugin in a less error-prone manner than is currently required.
But anyway:
This is the exactly the procedure that DcUpdater uses when updating plugins.
Though i think it would be even more useful if we wrote a generic installer for plugins and added a way for FARR itself to guide user through installing a plugin in a less error-prone manner than is currently required.
But anyway:
- If you want to signal FARR to *UNLOAD* all plugins, in preparation for updating a dll that might currently be in use, send the FARR process the windows message WMUSER with WPARAM=98 and LPARAM=97. You would normally do that BEFORE you try to install or replace any dll.
- Then to signal FARR that the installation is completed and that FARR should *reload* its plugins, send the windows message WMUSER with WPARAM=98 and LPARAM=98. You would normally do this after your installer has finished.
This is the exactly the procedure that DcUpdater uses when updating plugins.










):
