Template comparison:

• VS 2005 + Orcas extensions: WCF Service Library
• VS 2008: WCF Service Library

The new template in VS 2008 has not changed much. The main difference is the naming convention of project files generated, the separation of service contract and service type files, and the sample service contract and service type code is slightly different.

Impact to Learning WCF labs:

Anywhere I ask you to create a WCF Service Library, you should follow the same steps. The difference will be in the file location where the service contract and service type is located.

• When I ask you to modify the names of the service file I usually have you use the service name, for example, HelloIndigoService.cs. Now, you will rename the service contract source file to use an "I" prefix (for example, IHelloIndigoService.cs) and rename the service type source file to my original recommendation (for example, HelloIndigoService.cs).
• When I ask you to modify code for the service contract or service type, you can modify them in their respective source files. There is no need to merge the two into one file.

Summary of WCF Service Library in VS 2008:

The most likely scenario for creating a new WCF service is to create a new WCF Service Library. That is, a class library assembly with a service contract and service type within. Select the template as shown here:

It generates the same result as VS 2005 with Orcas extensions, except that the service contract and service type are in separate files (IService1.cs and Service1.cs):