skip to content »

Validating an xsd

Online retrieval follows either the WS-Metadata Exchange protocol or the DISCO protocol (for details see the Metadata Download section).

These metadata documents can be on a durable storage, or be retrieved online.If this option is used, an executable assembly with an associated configuration file must be passed as input.searches all associated configuration files for the service configuration.However, if you want to process metadata files on the local file system, you must specify all files in this argument.In this way, you can use Svcutil in a build environment where you cannot have network dependencies.You should provide either a language name registered in the Machine.config file, or the fully-qualified name of a class that inherits from Code Dom Provider.

Values: c#, cs, csharp, vb, visualbasic, c , cpp Default: csharp Short form: Specifies a mapping from a WSDL or XML Schema target Namespace to a CLR namespace.

All generated types will either be in the default namespace or the namespace specified by '*'. When generating clients, use this option to specify assemblies that might contain types that represent the metadata being imported.

You cannot specify message contracts and Xml Serializer types using this switch.

The Service Model Metadata Utility tool is used to generate service model code from metadata documents and metadata documents from service model code.

The Service Model Metadata Utility Tool can be found at the Windows SDK installation location, specifically, C:\Program Files\Microsoft SDKs\Windows\v6.0\Bin The following table summarizes the various functionalities provided by this tool and the corresponding topic that discusses how it is used.

Short Form: Specifies the fully-qualified or assembly-qualified name of a type to be excluded from export.