Steps to Deploy the WCF service to IIS on Windows XP

On the Windows Start menu, click Run. In the Run dialog box, type inetmgr, and then click OK. The Internet Information Services console starts. In the Internet Information Services console, expand the node corresponding to your computer in the tree-view, and then expand Web sites. Right-click Default Web Site, point to New, and then click Virtual Directory. The Virtual Directory Creation Wizard starts. In the Welcome to the Virtual Directory Creation Wizard page, click Next. In the Virtual Directory Alias page, type ProductsService, and then click Next. In the Web Site Content Directory page, click Browse, select the folder Microsoft Press\WCF Step By Step\Chapter … Click here to continue…..

Steps to Deploy the WCF service to IIS on Windows Vista

In the Windows Control Panel, click System and Maintenance, click Administrative Tools, and then double-click Internet Information Services (IIS) Manager. The Internet Information Services (IIS) Manager starts. In the Internet Information Services (IIS) Manager, expand the node corresponding to your computer in the tree-view, and then expand Web sites. Right-click Default Web Site, and then click Add Application. The Add Application dialog box appears. In the Add Application dialog box, in the Alias text box type ProductsService. Click the browse button (with the ellipses “…”) adjacent to the Physical path text box. In the Browse for Folder dialog box, select the folder Microsoft Press\WCF Step … Click here to continue…..

WCF bindings comparison

Binding Protocol/Transport Message Encoding Security Default Session Transaction Duplex BasicHttpBinding Http, Https Text None No – – WSHttpBinding Http, Https Text Message Optional Yes – WSDualHttpBinding Http, Https Text Message Yes Yes Yes NetTcpBinding TCP Binary Transport Optional Yes Yes NetNamedPipeBinding Named Pipe Binary Transport Yes Yes Yes NetMsmqBinding MSMQ Binary Transport Yes Yes No WSFederationHttpBinding Http, Https Text Message Yes Yes No NetPeerTcpBinding P2P Binary Transport – – Yes MsmqIntegrationBinding MSMQ Not Supported Transport Yes Yes –

Difference between Basic HTTP Binding and Net TCP Binding in WCF Service

Juval Lowy’s book said – “A binding is merely a consistent, canned set of choices regarding the transport protocol, message encoding, communication pattern, reliability, security, transaction propagation, and interoperability.” Basic HttpBinding – HttpBinding is based on  HTTP protocol. It is compatiable with Web Service Technology and SOAP standard, which are heavier than TCP protocols. To make is SOAP compatible you need to write lot of header and extra stuff. More over you are working on a higher level of network layer when working with HTTP protocol, so there is some overhead as well. Main features are uses WS-I Basic Profile 1.1 … Click here to continue…..

Difference between BasicHttpBinding vs. WSHttpBinding in WCF Service

The BasicHttpBinding and the WSHttpBinding are designed for interoperability and they are the two most commonly used bindings. Both binding types work best in a load-balanced environment. For performance, the BasicHttpBinding has considerably less overhead than the WSHttpBinding. If you do not need the features that are specific toWSHttpBinding, use the BasicHttpBinding to improve performance. To illustrate the overhead of the WSHttpBinding, compare two simple messages that invoke the GetDataoperation. (This operation is automatically created by using the WCF Service Application project template in Visual Studio.) One message was sent by the BasicHttpBinding. The other was sent by the WSHttpBinding. … Click here to continue…..