Apparently, if you show some method which is never called (called, not "hit"), and nothing except this method, you don't show the code where your problem is. The problem is always outside this method. Isn't this obvious?
Besides, I cannot be 100% sure that your conclusion that the method is never called. Debugging of a Windows Service is not such a trivial thing. I'm not even sure you attempted to start the Service correctly. It cannot be started as a regular application. It won't behave like a Service unless it is started by a Service Controlled, which is a special application host.
So, you should get one of the basic principles, and this is all, based on the information you provided. From this point, you can start your investigation. Here is a hint for you: if this method is not called, you did not even start developing a Windows Service. Please see:
http://msdn.microsoft.com/en-us/library/y817hyb6.aspx[
^],
http://msdn.microsoft.com/en-us/library/zt39148a.aspx[
^].
—SA