[Mono-list] Problem with mono WCF (compatibility with .NET ??)
Atsushi Eno
atsushieno at veritas-vos-liberabit.com
Tue Apr 27 02:17:13 EDT 2010
Hello,
On 2010/04/27 0:59, Jspoon wrote:
> Hi,
> I transfer hash password over basicHttpBinding wcf service. I use mono 2.6.3
> release.
> If I hosting WCF service on .NET server and client is on Mono, this error
> occured (always):
>
> Exception in async operation: System.Xml.XmlException: Referenced character
> was not allowed in XML
> ...
> Referenced character was not allowed in XML. Normalization is True,
> checkCharacters = True Line1, position 542
>
>
>
If there are not allowed characters in XML, then it will be raised. But
there are couple of other chances that it's not receiving expected XMLs.
For example, some people use BinaryMessageEncodingBindingElement with
HttpTransportBindingElement, which might bring wrong (unexpected) binary
format error.
Can you post the actual code that reproduces your problem?
And it'd be a lot nicer if you try mono from trunk instead of old 2.6.3.
> If hosting WCf service on Mono server and client is on .NET, this error
> sometimes (3 times from 5) occured:
>
> Addressing Version AddressingNone does not support adding WS-Addressing
> headers
>
>
It's likely due to problematic ServiceMetadataBehavior issue, but it's
anyways hard to tell exactly without code.
> And if hosting WCF service on Mono and client is on Mono too, this error
> occured (always):
> ...
> System.ServiceModel.FaultException 1
> ...
> invalid character at 0:&#@$
>
>
I'm not sure what's going on there, but remember I mentioned Binary
message encoder above.
> On .NET hosting and client all running fine.
>
>
> What's wrong please? Is it compatibility problem with WCF .NET and Mono WCF.
>
Atsushi Eno
More information about the Mono-list
mailing list