Re: [Wrapper-user] Service dependencies

[Leif M. <le...@ta...>]

Sylvain,
Please post requests to the user list rather than to me directly.

The shutdown problem is not a wrapper bug. It is a problem with the way the
Windows OS handles the shutdown of services. An OS bug / design flaw.

Unfortunately as you pointed out, it sounds like the communications service
is being shutdown before the wrapper's service. There is no way to
control the
shutdown order.

Is there always a user logged on your system? One option would be to trap
the logout event of the user just before the shutdown. You will always
get that
a couple seconds before the wrapper service gets shot down. It wouldn't be
reliable but it might give you enough time to get the message out before the
communications service gets shutdown.

Ceers,
Leif

Sylvain Bond wrote:
>
> Hi
>
> I have been using your Service wrapper and it works well, but I got a
> question for you.
>
> I am trying to trap windows event and seng a message through a COM
> Port before windows shuts down but it looks like COM Ports become
> closed before my service try to send a message. I did try to put some
> depedencies on my service to a few windows services but I am not sure
> which handles COM Ports. I also saw in your documentation that there
> is a known bug about windows and services dependencies when it comes
> to a shut down.
>
> So basically I cannot make my application send the message before
> windows closes his COM Ports.
>
> Do you have any suggestions or solutions on how I could manage to send
> a message through a COM Port when my service traps a shut down event ?
>
> Thank you
>
> Sylvain
>