0 out of 1 rated this helpful - Rate this topic

XsdDataContractExporter Class

Allows the transformation of a set of .NET Framework types that are used in data contracts into an XML schema file (.xsd).

Namespace:  System.Runtime.Serialization
Assembly:  System.Runtime.Serialization (in System.Runtime.Serialization.dll)
public ref class XsdDataContractExporter

Use the XsdDataContractExporter class when you have created a Web service that incorporates data represented by common language runtime (CLR) types and when you need to export XML schemas for each type to be consumed by other Web services. That is, XsdDataContractExporter transforms a set of CLR types into XML schemas. (For more information about the types that can be used, see Types Supported by the Data Contract Serializer.) The schemas can then be exposed through a Web Services Description Language (WSDL) document for use by others who need to interoperate with your service.

Conversely, if you are creating a Web service that must interoperate with an existing Web service, use the XsdDataContractImporter to transform XML schemas and create the CLR types that represent the data in a selected programming language.

The XsdDataContractExporter generates an XmlSchemaSet object that contains the collection of schemas. Access the set of schemas through the Schemas property.

NoteNote:

To quickly generate XML schema definition (XSD) files that other Web services can consume, use the XsdDataContractExporter.

Exporting Schemas Into an XmlSchemaSet

To create an instance of the XmlSchemaSet class that contains XML schema files, you should be aware of the following.

The set of types you are exporting are recorded as an internal set of data contracts. Thus, you can call the CanExport method multiple times to add new types to the schema set without degrading performance because only the new types will be added to the set. During the Export(IListAssembly) operation, the existing schemas are compared to the new schemas being added. If there are conflicts, an exception will be thrown. A conflict is usually detected if two types with the same data contract name but different contracts (different members) are exported by the same XsdDataContractExporter instance.

Using the Exporter

A recommended way of using this class is as follows:

  1. Use one of the CanExport overloads to determine whether the specified type or set of types can be exported. Use one of the overloads that is appropriate to your requirements.

  2. Call the corresponding Export method.

  3. Retrieve the schemas from the Schemas property.

The following example creates an instance of the XsdDataContractExporter and calls the Export(Type) method.

No code example is currently available or this language may not be supported.
System::Object
  System.Runtime.Serialization::XsdDataContractExporter
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Windows 7, Windows Vista, Windows XP SP2, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003

The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

.NET Framework

Supported in: 3.5, 3.0
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.