you can debug live in vs2012 or vs2010 with breakpoints now and see what happens.
Announcement
Collapse
No announcement yet.
Bug reporting & changes
Collapse
X
-
Originally posted by Rick Tinker View PostIt would compile fine - the only thing the compiler checks is that it is there, if you referenced the interface that calls for it which you did.
Wondering if there is an object issue? Is ShutDownIO in a module file or a class object?
Why not just put it in the HSPI object?
Comment
-
I use the ShutdownIO to end all of my threads, close down the database and close any debug logging.
I see this error in the HS log when I shutdown a single plugin down.
4:26:40.559 PM Error Shutting down plugin: Object reference not set to an instance of an object.
(System)_05-Dec-2012 16:26:40.5875_Web Server Read Callback Thread
Comment
-
While looking at this issue, we came to the conclusion that an additional piece of code should be added to Main.vb.
Right after the line:
Loop While client.CommunicationState = HSCF.Communication.Scs.Communication.CommunicationStates.Con nected And Not plugin.gShutDown
You should add:
If Not plugin.gShutDown Then plugin.ShutdownIO()
This allows for the situation when the server is inadvertantly disconnected from the plugin to allow the plugin to shut down in an anticipated manner.
Please note, while this does stop the issue of ShutdownIO not always being run, this is not the way we are fixing it...., Rich is currently looking into why the client sometimes disconnects prior the ShutdownIO being run, and will correct it in a future build.Wade
"I know nothing... nothing!"
Comment
-
Originally posted by Sgt. Shultz View PostWhile looking at this issue, we came to the conclusion that an additional piece of code should be added to Main.vb.
Right after the line:
Loop While client.CommunicationState = HSCF.Communication.Scs.Communication.CommunicationStates.Con nected And Not plugin.gShutDown
You should add:
If Not plugin.gShutDown Then plugin.ShutdownIO()
This allows for the situation when the server is inadvertantly disconnected from the plugin to allow the plugin to shut down in an anticipated manner.
Please note, while this does stop the issue of ShutdownIO not always being run, this is not the way we are fixing it...., Rich is currently looking into why the client sometimes disconnects prior the ShutdownIO being run, and will correct it in a future build.
If Not HSPI.bShutDown Then plugin.ShutDownIO()
I assume you meant bShutdown instead of gShutdown
bShutdown is public shared
Comment
-
I took it from one on mine, rather than the sample, so it very well could be. The boolean value to check is the one being set in the shutdownIO function, which is the same as the one being checked in the loop.
The names change, but the code remains the same.Wade
"I know nothing... nothing!"
Comment
Comment