WCF generated XSD and ExtensionDataObject

Hot Topic

Deadlocks using duplex contracts
Hosting Multiple Services
If I add the comp's source to the solution, then it works I can debug into, but
Trouble renaming files in SS 6.0
SecurityException while Displaying image using BitmapImage in web browser application
Any known issues while using VS2003 & VS2005 side by side with VSS6 ?
No Debug or Release drop down
==> I need help. Add-in 101 <==
Where can I find ANY information about sourcesafe 2005?
Extending a DSL post-deployment

Visual Studio

msbuild task
Javascript Error with report viewer 'oReportDiv' is undefined.
how to allow paging, group tree selection and exporting
Extra Page while exporting to PDF from Crystal Reprot
Writing add-in for VisualStudio.Net 2003
VS 2005 Install woes
Testing
Help (other things too) broken? Team Suite
Addressing trailing whitespace, line endings, and custom mouse actions
connection to MSDN library directly(e.g., using F1)

WCF generated XSD and ExtensionDataObject

This line gets generated for all of my xsd objects, where is this coming from and how do I remove it from being generated in the XSD file.

<xs:element minOccurs="0" maxOccurs="1" name="ExtensionData" type="tns:ExtensionDataObject" />




Answer this question

WCF generated XSD and ExtensionDataObject

  • rain0x01

    The schema comes from a XSD designed with MSVS 2005, and then added to the project and used as request parameters, and response parameters in the WCF Operation Contract.

            [OperationContract(Name = "Test")]
            ResponseTest Test(TestReq req);

    ResponseTest and TestReq are both from the xsd in the project. So are you saying I can't use the xsd, I have to build DataContract classes for everything that is in the XSD.  I hope there is a way to connect the DataContract to the XSD in the project without having to rewrite a bunch of classes that reflect what is in the XSD.



  • Webdav101

    How are you getting the schema There are several different serialization programming models - e.g. the XmlSerializer model (that existed since .NET 1.0) and the new DataContract programming model (introduced in WCF). In general, if you run a tool designed for one programming model on classes that are designed with another programming model, you will get unexpected results. The correct way to get schema from Data Contract classes is to use the svcutil.exe tool (you can use the "/dconly" switch to only generate schema). If you do that, you will not get the extra "ExtensionData" element. However, if you use the old "xsd.exe" tool (that was never designed for the new Data Contract programming model) you will get schema that may be incorrect in many ways, including this extra "ExtensionData" element.

  • WCF generated XSD and ExtensionDataObject
Answer this question