Windows Service class constructor and OnStart method

I don't know whether there's anything written down by MS about this but my own view is that:

1. You should only put initialization code for the service in the constructor, namely the call to InitializeComponent() if you're using VS followed by any other initialization which can't be done simply by setting property values in the Properties Box. Remember that the constructor will only be called once even if the service is stopped and then restarted again, so you only want stuff in here which isn't going to change.

2. You should only put code required to start the service in the On Start() method. This includes code to create resources needed by the service and code to create and launch a new thread or threads. Remember that, if the service may be stopped and restarted, then you may need to release those resources in the OnStop() method and recreate them again in OnStart().

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

George George18y ago
Thanks Alan,

Question answered.

regards,

George
0
Alan18y ago
I don't know whether there's anything written down by MS about this but my own view is that:

1. You should only put initialization code for the service in the constructor, namely the call to InitializeComponent() if you're using VS followed by any other initialization which can't be done simply by setting property values in the Properties Box. Remember that the constructor will only be called once even if the service is stopped and then restarted again, so you only want stuff in here which isn't going to change.

2. You should only put code required to start the service in the On Start() method. This includes code to create resources needed by the service and code to create and launch a new thread or threads. Remember that, if the service may be stopped and restarted, then you may need to release those resources in the OnStop() method and recreate them again in OnStart().
0