Creating Self Signed Certificate – Link

When developing a secure service or client using Windows Communication Foundation (WCF), it is often necessary to supply an X.509 certificate to be used as a credential. The certificate typically is part of a chain of certificates with a root authority found in the Trusted Root Certification Authorities store of the computer. Having a certificate chain enables you to scope a set of certificates where typically the root authority is from your organization or business unit. To emulate this at development time, you can create two certificates to satisfy the security requirements. The first is a self-signed certificate that is placed in the Trusted Root Certification Authorities store, and the second certificate is created from the first and is placed in either the Personal store of the Local Machine location, or the Personal store of the Current User location. Read more from the below link …

http://msdn.microsoft.com/en-us/library/ms733813.aspx

Thanks to my colleague as it is a new learning from him.

WCF – Links

http://www.wcftutorial.net

http://beyondrelational.com/blogs/dhananjaykumar/archive/2011/02/11/walkthrough-on-creating-wcf-4-0-service-and-hosting-in-iis-7-5.aspx

WCF Fact Matrix

Hosting Environment	Platform Availability	Transports Supported	Process and AppDomain Recycling	Key Benefits and Limitations	Common Scenarios
Managed Application (“Self-Hosted”)	1. Windows XP 2. Windows Server 2003 3. Windows Vista 4. Windows Server 2008	HTTP net.tcp net.pipe net.msmq	No	1. Flexible. 2. Easy to deploy. 3. Not an enterprise solution for services.	1. Console applications used during development. 2. Rich WinForm and WPF client applications accessing services.
Managed Windows Service	1. Windows XP 2. Windows Server 2003 3. Windows Vista 4. Windows Server 2008	HTTP net.tcp net.pipe net.msmq	No	1. Service process lifetime controlled by the operating system, not message-activated. 2. Supported by all versions of Windows. 3. Secure environment.	A long-running WCF service hosted outside of IIS
IIS 5.1	Windows XP	HTTP	Yes	1. Process recycling. 2. Idle shutdown. 3. Process health monitoring. 4. Message-based activation. 5. HTTP only.	Running a WCF service side-by-side with ASP.NET content on the Internet using the HTTP protocol.
IIS 6.0	Windows Server 2003	HTTP	Yes
Windows Process Activation Service (WAS)	1. Windows Vista 2. Windows Server 2008	HTTP net.tcp net.pipe net.msmq	Yes	1. IIS is not required. 2. Process recycling. 3. Idle shutdown. 4. Process health monitoring. 5. Message-based activation. 6. Works with HTTP, TCP, named pipes, and MSMQ.	Running a WCF service without installing IIS on the Internet using various transport protocols.
IIS 7.0	Windows Server 2008	HTTP net.tcp net.pipe net.msmq	Yes	1. WAS Benefits 2. Integrated with ASP.NET and IIS content	1. Running a WCF service with ASP.NET content. 2. Running a WCF service on the Internet using various transport protocols

Refer http://msdn.microsoft.com/en-us/library/ms730158.aspx for more details.