Callbacks into another assembly

[David]

Here's my problem. I've created a windows service using the Win32 app
instead of the .NET framework's System.ServiceProcess.ServiceBase and
I'm trying to use the RegisterServiceCtrlHandler win32 API call. It
works just fine when I compile all my code and classes in a normal
executable. However, when I throw it into a class library, it can't
seem to find the control handler function. It seems like it's a problem
with the callback into the external assembly. Any suggestions?

Thanks,
- David Hoyt

[David]

I meant "Win32 API," no "Win32 app." Sorry 'bout that!

[Richard Grimes]

David wrote:

Here's my problem. I've created a windows service using the Win32 app
instead of the .NET framework's System.ServiceProcess.ServiceBase and
So this is a .NET app, but you've used platform invoke to make the
appropriate calls through Win32 to the SCM?
I'm trying to use the RegisterServiceCtrlHandler win32 API call. It
works just fine when I compile all my code and classes in a normal
executable. However, when I throw it into a class library, it can't
Now I am confused. A service is a *process*, why are you compiling it
into a library?

It is possible to host a DLL based service in svchost.exe, however, this
is not documented and presumably Microsoft does not support it. Is this
what you are trying to do?
seem to find the control handler function. It seems like it's a
problem with the callback into the external assembly. Any suggestions?

Richard
--
http://www.grimes.demon.co.uk/workshops/fusionWS.htm
http://www.grimes.demon.co.uk/workshops/securityWS.htm

[David]

Hi Richard,

Thanks for your reply, I apologize for not explaining it clearly.
That's not exactly what I'm trying to do, but the p-invoke part is
correct. The ServiceBase class is an abstract base class used for
creating a service. It resides in its own dll that is referenced in
your own project, let's say. In your program, you would reference the
dll, create a class that derives from ServiceBase, override a few
methods, and compile your executable. The service is the compiled
program you made, but all the SCM calls are in the ServiceBase class
inside the referenced dll, much like System.ServiceProcess.ServiceBase.
The .NET framework's base class for a service does not reside in your
own executable - it's in its own dll in the GAC. Mine works almost
exactly the same. I hope that makes sense. So it's not a dll-based
service at all.