Guidance Automation Toolkit 2010 and Visual Studio 2010 Visualization and Modeling SDK if you are building the Service Factory 2010 source code.
Using Service Factory to create web service enabled solution is about designing with the Models (Service Contract, Data Contract and Host) then followed by choosing the required technology either ASMX or WCF available from the Service Factory. Finally, the projects and codes are generated into them. It is assumed that you have some working knowledge on WCF and this walk through focuses specifically on WCF. Here we go.
Service Contract Model
Let get start designing the service contract. Right click on the MyCompany.Service.Model.AppName project --> Add --> New Service Contract as shown in the following figure 1.3.
We repeat the same processes for the request and response messages for other Operation shapes on the design surface until we are done in figure 1.10. Notice the arrow of the connector for the request and response message.
Data Contract Model
From the figure 1.30, service factory generates the projects for all the layers correspond to the web service application layered diagram by grouping all the projects into their respective solution folders.
It is time to look at the content of the project mapping file (ProjectMapping.xml) . The purpose of this file is to decouple the models from the project that the service factory will generate codes into. Figure 1.31 shows the content of the project mapping file generated by the service factory initially
Figure 1.31 Content of the Project Mapping File
Modifying the service factory source code to emit the implementation projects to follow the desired naming for the namespace, assembly, project and also the location to create the project is the most ideal solution. This is the long term solution for the organization that has many ongoing service projects as the automation can avoid errors and unproductive works. It is worth the efforts and investment to customize the software factory to tailor to specific development needs.