Hosting in IIS 6.0
When you
expose WCF services over the Internet using HTTP protocol on a Windows Server 2003 machine,
IIS 6.0 provides a much richer hosting environment than self-hosting. Unlike self-hosting,
no code is required to instantiate ServiceHost instances,
but you can still use declarative configuration in the application’s web.config file. More importantly, IIS 6.0 provides other
much-needed hosting features for idle-time management, health monitoring, process recycling,
and management tools for configuring application pools.
In the first three chapters of this book, you have created ASP.NET web sites to host WCF services, completed labs that used the various WCF service templates to help get you started, and experienced some of the differences between self-hosting and IIS hosting. In this section, I’ll review how IIS hosting works in general terms, discuss its distinct behaviors and added value, and provide you with an architectural overview of the IIS 6.0 hosting environment. In addition, I’ll discuss ASP.NET compatibility mode, which allows you to host WCF services through the ASP.NET pipeline to assist with migration of ASP.NET web services.
IIS Service Endpoints
When you host your services with any version of IIS, you must provide at a minimum the following:
An addressable web site or virtual directory for your service endpoints
A file with the extension .svc that will help activate the
ServiceHostinstanceA service type that is linked to the .svc file for activation ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access