There a few properties of the HSPI class that are queried when HS3 starts up. It appears that some plugins are actually doing some work in these properties.
When HS3 starts it loads your plugin in a seperate AppDomain, loads the HSPI class, then queries the following properties:
Name
AccessLevel
Capabilities
comport
supportsMultipleInstances
supportsMultipleInstancesSingleEXE
The plugin is then unloaded. These properties should simply return values and not do any work such as launching threads.
Note that the New sub in the HSPI class will also be called and that sub should not contain any code. Do all initialization in InitIO.
Launching threads from any of the properties above, or from New, could caused HS to exit and not start up. Build 3.0.0.330 and later has some added checks to not allow HS to exit.
When HS3 starts it loads your plugin in a seperate AppDomain, loads the HSPI class, then queries the following properties:
Name
AccessLevel
Capabilities
comport
supportsMultipleInstances
supportsMultipleInstancesSingleEXE
The plugin is then unloaded. These properties should simply return values and not do any work such as launching threads.
Note that the New sub in the HSPI class will also be called and that sub should not contain any code. Do all initialization in InitIO.
Launching threads from any of the properties above, or from New, could caused HS to exit and not start up. Build 3.0.0.330 and later has some added checks to not allow HS to exit.
Comment