I actually did some work with this a while ago. A short description of what I did...
Switch all of the server projects from Executables to DLLs. I added some exported functions to initialize and cleanup each respective server.
I then wrote a master service that used a config file of its' own to figure out what DLLs to load and initialized them, how many zone servers to run etc...
It was working fairly well, but at the time the server sourcecode was at a fairly unstable state and when a new release came out I just tossed the changes with the intention of adding them again at a later date.
I wasn't using .NET but a good old Win32 ServiceMain etc... in theory you could go with the convert-them-to-dlls option and load them in a C# Windows Service with calls to the unmanaged DLLs... that could be interesting. You could also get some nifty features with the Service-oriented features of the .NET Framework, easy access to the event logs etc...
|