XsdDataContractExporter Class
Allows the transformation of a set of .NET Framework types that are used in data contracts into an XML schema file (.xsd).
Assembly: System.Runtime.Serialization (in System.Runtime.Serialization.dll)
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.
Note: |
|---|
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:
The following example creates an instance of the XsdDataContractExporter and calls the Export(Type) method.
using System; using System.Xml; using System.Runtime.Serialization; using System.Xml.Schema; public class Program { public static void Main() { try { ExportXSD(); } catch (Exception exc) { Console.WriteLine("Message: {0} StackTrace:{1}", exc.Message, exc.StackTrace); } finally { Console.ReadLine(); } } static void ExportXSD() { XsdDataContractExporter exporter = new XsdDataContractExporter(); if (exporter.CanExport(typeof(Employee))) { exporter.Export(typeof(Employee)); Console.WriteLine("number of schemas: {0}", exporter.Schemas.Count); Console.WriteLine(); XmlSchemaSet mySchemas = exporter.Schemas; XmlQualifiedName XmlNameValue = exporter.GetRootElementName(typeof(Employee)); string EmployeeNameSpace = XmlNameValue.Namespace; foreach (XmlSchema schema in mySchemas.Schemas(EmployeeNameSpace)) { schema.Write(Console.Out); } } } static void GetXmlElementName() { XsdDataContractExporter myExporter = new XsdDataContractExporter(); XmlQualifiedName xmlElementName =myExporter.GetRootElementName(typeof(Employee)); Console.WriteLine("Namespace: {0}", xmlElementName.Namespace); Console.WriteLine("Name: {0}", xmlElementName.Name); Console.WriteLine("IsEmpty: {0}", xmlElementName.IsEmpty); } [DataContract(Namespace = "www.Contoso.com/Examples/")] public class Employee { [DataMember] public string EmployeeName; [DataMember] private string ID; } }
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.
Note: