About WsdCodeGen
WsdCodeGen uses an XML configuration file to determine the location of the service metadata. The configuration file is also used to define interface names, interface GUIDs, class names, method names, and other identifiers. For more information about this file, see WsdCodeGen Configuration File.
WsdCodeGen requires two types of input files: an XML configuration file and one or more service description files (WSDL and/or XSD files). WsdCodeGen processes these input files and generates two type of output files: interface files and header/source files.
Input Files
| Type | Description |
|---|---|
| Configuration file | An XML file that indicates the location of the service metadata and defines interface names, interface GUIDs, class names, method names, and other identifiers. |
| Service description files | One or more WSDL or XSD files that describes the services to implement on the device. |
Output Files
| Type | Description |
|---|---|
| Interface files | An IDL (Interface Definition Language) file that can be used with the MIDL compiler to produce an interface header file. WSDAPI clients and WSDAPI services can use this interface file. |
| C++ header and source files | C++ files that describe the message contract, namespace, and type information. They may contain proxy code and/or stub code. Proxy code implements a service's interface and translates service method calls into WSDAPI operations that make service requests. Stub code translates WSDAPI service requests into code that calls service methods. |
Related topics
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for