Hosting WCF service in IIS using WAS (Hosting WCF with Non-Http protocol)

By defaults IIs supports only http protocol. If you want to use non-http protocols like TCP, you need to install "Windows Communication Foundation Non-Http Activaion" component and WAS(Windows process Activation Service) component. WAS is supported with IIS7 and above.

To Support NON-HTTP protocols in IIS, you need to follow the following steps.

1. Install WAS and WCF Non-Http Activation component
2. Enable Non-Http protocol support in IIS for your application

Step 1 : (Install WAS and WCF Non-Http Activation component)

1. Go to control panel
2. Click program and features
3. Click on Turn windows features on or off option
4. Expend .NetFramework and select "WCF Non-Http Activation"
5. Click OK

Step 2 : (Enable Non-Http protocol support in IIS for your application)

1. Open IIS
2. Right Click on your application--Manage Application--Advance Setting
3. In Advance setting window, set Enabled Protocol- http, net.tcp
4. Click OK

Now run service, Create client, Add reference of service and enjoy service.

Related Topics :

Different-option-of-hosting-wcf-service
Binding-in-wcf-choosing-right-wcf-service
Exchanging-metadata-in-wcf
Some-interesting-facts-about-data-contract
Knowntype-attribute-in-wcf
Associating-knowntype-in-wcf
Message-contract-in-wcf
Exception-handling-in-wcf
Exception Handling in WCF - SOAP Fault in WCF
Exception Handling in WCF - Unhandled Exception in WCF
Exception Handling in WCF - Creating and Throwing Strongly Typed SOAP Fault