> We have many separate components which we want to deploy on > an application server. It seems sensible that each component > is hosted in a separate service so that it can be > deployed/stopped/started independently of the other components. > > I have tried hosting two components in the same service and > this works fine but is not practical(you would have to > rebuild the service for each new component).
It seems to me that it should be fairly straightforward to build a single, generic service with a sort of plugin architecture, whereby you simply add a DLL to a directory, maybe restart the service, and it scans through the dir, loading and "starting" each of the components it finds there. Would that solve your problem? No need to rebuild the service, you have one process, and if the generic service code calls ChannelServices.RegisterChannel, all the components need to do is to RegisterWellKnownServiceType on whatever endpoints they want to expose to make use of it, without even having to know what it is. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
