A number of files are generated including three different XSD schemas.

These
schemas describe the data types contained in the service contract. We also get two
BizTalk binding files: one for the adapter type used in the metadata request (in
our case, WCF-NetNamedPipe) and another we can optionally use to configure a WCF-
Custom send port. In addition, the wizard emitted a new orchestration, which
contains type definitions for multi-part messages representing the contract
schemas, and, a port type that reflects the message exchange pattern of the target
service.

Back in our primary orchestration, we now add the messages used for calling the
service and handling the response. These messages
(Contact_Request,Contact_Response) are created by using the multi-part message
types defined in the wizard-generated orchestration.