tags:

views:

20

answers:

0
+2  Q: 

SvcUtil and 'System.Xml.Linq.XElement' cannot be converted to 'System.Xml.XmlElement' compiler error

I always recieve the above error when I generate a proxy class for my service using SvcUtil. The service is exposing a property that is of System.Xml.Linq.XElement type. The SvcUtil generates a System.Xml.XmlElement type property unfortunately. On the other hand if I'm using Add Reference in VS to generate the proxy class, everything's ok. I tried the latest 4.0 version of SvcUtil from the NETFX 4.0 Tools folder, but still with no luck.

related questions

C# and WCF - svcutil not generating wrapper correctly for string[]
svcutil fails against service with a fault contract
SVCUtil or WSDL batch processing
How do I export metadata for a single contract with svcutil.exe?
Is there a way to force svcutil.exe to ignore SSL certificate issues?
WCF service reference namespace differs from original
Can i provide my own ArrayOfstring to svcutil?
svcutil.exe redundant proxy classes
use svcutil to map multiple namespaces for generating wcf service proxies
Generated WCF proxy configuration uses server's local name
svcutil.exe - Proxy generated not allowing for nullable fields
wsdl + svutil
Problem with generating WebService proxy using svcutil
methods with the same soapaction
WCF: Svcutil generates invalid client proxy, Apache AXIS Web Service, overload operations
SvcUtil not generating abstract classes in the client proxy (WCF)
svcutil omits the ServiceKnownType attribute from the generated interface proxy.
Generating Client Proxy from a Windows Service
MSBuild WCF Options
Impossible to use WSDL definition
how to generate custom collection type in .Net from WSDL?
Identical Types In Separate Web Services
Can I force svcutil.exe to generate data contracts for a WCF service?
Does Visual Studio 2008 Use SvcUtil.exe and if "No" is there any disadvantage to using svcutil?
Sharing types in WCF using VS 2008 not working