Self-Hosting of WCF services

re: Self-Hosting of WCF services

Damir Dobric — Sun, 06 Jul 2008 13:00:35 GMT

You are right Marco. Unfortunately our problem is not to find a way how to do it, because we already have several possible ways. I think, that we need at the Microsoft platform the server product or whatever, which is just able to host anything. How about Server which host WCF-services (by using of any possible binding), Workflows, Biztalk orchestrations, Sharepoint Workflows (if it would be then any difference in comparison to native WF ) and event APS.Net and Sliverlight sites?

I hope and wander in the same time that Microsoft is going to do this as a part of Oslo project.

re: Self-Hosting of WCF services

marco — Mon, 11 Feb 2008 16:47:34 GMT

You could easily host the self-hosted WCF service in a windows NT service, and it will be always on.

If you use must use Winows Server 2003, without WAS, the http only binding could be a major limitation, imho. So, I would not be so strict saying that self-hosting is only for debug.

re: Self-Hosting of WCF services

Vadym — Fri, 16 Nov 2007 15:16:11 GMT

Yes, there are some limitations, however if WCF service is hosted in the Windows Service then "Limited Availability" is not an issue.

Self-Hosting Services

Same Old Applications — Fri, 09 Nov 2007 15:13:47 GMT

Damir, in his Self-Hosting of WCF Services , writes about advantages and disadvantages of self-hosting