« WCF server startup slow on W2K3 in VM | Main | Defining KnownTypes in a configuration file »

09/05/2006

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a012876b389bb970c012876c21757970c

Listed below are links to weblogs that reference Start ServiceHosts for all configured Services:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Nicholas Paldino [.NET/C# MVP]

While services will more than likely have the same lifetime as an app-domain, they are in no way required to live for the life of the app-domain that they are in. You should expose a way to shut down a particular service as well.

Ingo Rammer

Absolutely. It just appears to me that, whenever you want to start/stop services on demand, you will quite likely have a need for more fine grained startup/shutdown behavior (only starting/stopping a subset of them depending on your runtime conditions). In this case, I would rely on ServiceHost as it exists today. Other than that, a CloseAllService() would be as simple as public static void CloseAllServices() { foreach (ServiceHost hst in _hosts) { hst.Close(); } } Cheers, -Ingo

Ujin

Absolutely. It just appears to me that, whenever you want to start/stop services on demand, you will quite likely have a need for more fine grained startup/shutdown a href=http://www.dornfall.combehavior/a

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Shared items (Google Reader)