VS2010将System.Xml.XmlElement与System.Xml.Linq.XElement混淆？

Question

I have created a WCF service with one method which returns a System.Xml.XmlElement :

Interface:

[ServiceContract]
public interface IWCFService
{
    [OperationContract]
    XmlElement Execute(...);
}

Service:

public XmlElement Execute(...)
{
    XmlNode node = ...;

    return (XmlElement)node;
}

When I try to access the service deployed on my server

WCFServiceClient service = new WCFServiceClient("WSHttpBinding_IWCFService");
XmlElement node = service.Execute(...);

I get the error:

Cannot implicitly convert type 'System.Xml.Linq.XElement' to 'System.Xml.XmlElement'

Searching my service solution, I cannot see any reference to System.Xml.Linq.XElement . Is it wrong of me to expect a System.Xml.XmlElement or is VS 2010 fooling around with me?

Answer 1

What I have found works the best and easiest for me is to right-click on the service reference and then click on "Configure Service Reference". Once in the dialog box for this at the bottom you will see 2 radio buttons that say "Reuse types in referenced assemblies" or "Reuse types in referenced assemblies". Click on the 2nd option for 'specified assemblies'. The listbox will then be enabled and you can check all assemblies and leave System.Xml.Linq . This way every time you update the service reference you will get the expected results and this will be stored in the configuration of the client.

Answer 2

1）从客户端删除system.xml.linq引用2）更新服务引用3）重新生成的Reference.cs文件现在将引用XmlElement而不是XElement

Answer 3

I hate to answer my own question, but here it goes:

As far as I can see, the System.Xml.XmlElement CAN be used as a return type for a WCF service. The DataContractSerializer used by default in WCF does support this type and thus it shouldn't be necessary to use the XmlSerializer .

However my problem has nothing to do with serializing, but thanks to Raj Kaimal for suggesting this possibility.

I followed the WCF tutorials given by Microsoft, which tells you to add the WCF service as a Service Reference when you want to use the service. This seems to be okay in VS2008, but when switching to VS2010 this approach changes the return type from System.Xml.XmlElement to the (newer?) System.Xml.Linq.XElement . To solve this, you need to add the service as a Web Reference instead.