quick update:
Explicitly specifying the Action and ReplyAction Attribute makes it
work. That's an OK workaround at least for me:
[OperationContract(Action = Foo, ReplyAction = FooReplay)]
void Foo();
Bug's also posted with ID 658520 by Maciej Kopańsk
Cheers,
Karsten
Karsten Fourmont
Hi,
while trying to access a Mono WCF service with a MS.NET client I
encountered issues with DateTime (de)serialization: it seems mono
serializes only the ticks and not the DateTimeKind info (UTC, Local,
Unspecified).
See bug 660424 for description and proposed fixed. (I posted it as WCF
bug
Sorry for cross posting but I think I should have posted this in the dev
forum in the first place.
I'm a .NET Windows guy and not a guru on Linux but with Justin Malcom's help
I have the latest 2.8.1 mono installed on an older RHEL45 dev system and it
seems to be working quite well and is quite
Just a thought - if using WCF, the client and server could be in different
zones so why would you want anything other than UTC time to be passed around
in the first place which is always what should be stored and only converted
when displayed using the local conventions. The zone is not part of
Well, date and time information can sure be locale independent, but
NET's DateTime values aren't. It also contains DateTimeKind flag and
ToBinary() adds that information within the 64 bit return value in
addition to UTC time ticks.
So, Karsten is right and that is indeed a good point. I'll
