WCF Service Library vs Class Library project types

Question

What does a WCF Service Library do that a regular class library doesn't?

Edit: I posted my own answer. Am I missing anything? Are they fundamentally both just class libraries with a few template classes added?

Answer 1

I created both and compared. This is what I found.

WCF Service Library

• adds references to System.Runtime.Serialization and System.ServiceModel. does not contain a reference to System.Data.DataSetExtensions as the Class Library does.
• contains sample service classes IService1, CompositeType and Service1
• adds app.config with a wsHttpBinding and a mexHttpBinding service endpoint
• adds /client:"WcfTestClient.exe" as a debug command line option in the project properties
• adds a WCF Options tab in the project properties. This tab contains an option to start a WCF service host when debugging another project in the same solution
• enables a Sign the ClickOnce manifests option in the Signing tab of the project properties. this option is disabled in the Class Library

Answer 2

It also runs the WCF Service Host utility on F5. The /client switch that you noticed is being passed to the WCF Service Host to tell it which client to launch. In this case, it is being told to launch the WCF Test Client.

This gives you a pretty good F5 experience. Set breakpoints in your service, hit F5, use the Test Client to invoke your service operation, and your breakpoints will be hit.

Answer 3

I have tested in VS 2010 project, using class library as WCF Hosting type, but it fails to generate wsdl or proxy classes.

WCF project is different than normal class library, because it adds many dlls in solution/project references and also it adds (Service1.svc) template, which you need to deploy in IIS server and to create 2 output files using svcutil.exe.

Mohammed Hoq