Hosting a WCF service in IIS enables scalable, reliable HTTP access with automatic lifecycle management. 1. Create a WCF Service Application in Visual Studio with a service contract, operation contract, .svc file, and web.config. 2. Configure web.config with endpoints using basicHttpBinding or wsHttpBinding, enable metadata exchange (MEX), and set service behaviors for metadata and debugging. 3. Publish the project and deploy to IIS by creating a website or application, setting the physical path, and assigning a matching .NET Framework application pool. 4. Test via browser at http://localhost/YourService/Service1.svc; verify MEX is working and resolve common issues like framework version mismatches, missing HTTP Activation feature, or incorrect permissions. Clients can then add a service reference using the .svc URL. Proper configuration ensures smooth deployment and consumption of WCF services through IIS.

Hosting a WCF service in IIS (Internet Information Services) is a reliable and scalable approach, especially for services that need to be accessed over HTTP. This setup allows IIS to manage the service lifecycle, handle activation, and provide built-in features like process recycling and security.

1. Prepare Your WCF Service

Create a WCF Service Application in Visual Studio or use an existing one. The project should include:

• A service contract ([ServiceContract])
• One or more operation contracts ([OperationContract])
• A .svc file that points to your service class
• A web.config file with proper WCF configuration

Example IService1.cs:

[ServiceContract]
public interface IService1
{
    [OperationContract]
    string GetData(int value);
}

Ensure your Service1.svc has the correct directive:

<%@ ServiceHost Language="C#" Debug="true" Service="WcfService1.Service1" %>

2. Configure web.config

The web.config must define at least one endpoint with a binding suitable for IIS (like basicHttpBinding or wsHttpBinding).

Example configuration:

<system.serviceModel>
  <services>
    <service name="WcfService1.Service1">
      <endpoint address="" binding="basicHttpBinding" contract="WcfService1.IService1" />
      <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
    </service>
  </services>
  <behaviors>
    <serviceBehaviors>
      <behavior>
        <serviceMetadata httpGetEnabled="true"/>
        <serviceDebug includeExceptionDetailInFaults="false"/>
      </behavior>
    </serviceBehaviors>
  </behaviors>
</system.serviceModel>

This enables metadata exchange (MEX), which lets clients generate proxies using "Add Service Reference".

3. Publish and Deploy to IIS

Publish your WCF project from Visual Studio:

• Right-click the project → Publish
• Choose a target (e.g., Folder, IIS on localhost)
• Deploy the output to an IIS site or application folder

In IIS Manager:

• Create a new website or application under Default Web Site
• Set the physical path to your published files
• Assign an appropriate application pool (.NET Framework version must match your project)

4. Test the Service

Navigate to the service URL in a browser, e.g.:

You should see the default WCF help page. If you get an error, check:

• .NET Framework version in the app pool
• HTTP Activation feature enabled in Windows Features
• Correct file permissions on the IIS folder
• web.config syntax and service name matching

From a client application, use "Add Service Reference" with the .svc URL to consume the service.

Basically, hosting WCF in IIS simplifies deployment and management for HTTP-based services. Just ensure the environment supports WCF HTTP activation and the configuration is accurate.

The above is the detailed content of How to host a WCF service in IIS. For more information, please follow other related articles on the PHP Chinese website!