KingSparta: We know about changing the registry entry, but that will cause the Plugin to load at startup, rather than when the user selects it. I can think of two problems with this approach.
1. It takes a lot of time and resources loading controls that don't need to be used.
2. It can be dangerous for plugins that are designed to take certain actions when started or initialized.
We were just hoping for the means of creating the plugin on first use, and not unloading until directed by the plugin, not on loss of focus, preferably without having to load it at startup.
I suppose it would be possible to have a Plugin that does nothing upon initialization, certain things upon activation, and can lose focus without exiting that could be run at startup. Just not what we had hoped for.
-Tano