This is one of those thing which is by design.
We have decided not to serialize remoting format as it is more of a runtime
parameter to do serialization and not an intrinsic state property of the
cache itself.
We would not have had a property like this on the dataset if we had some way
of informing the remoting architecture through a parameter that the
serialization should happen in XML or Binary. Since this was not possible,
we came up with this property on the dataset but decided not to round-trip
the value.
This is the same reason why we do not serialize this RemotingFormat property
through msdata annotation even when serializing to XSD through
ds.WriteXmlSchema.
HTH,
Ravinder
"Mark Walsh (KAZ Technology Services)"
<(E-Mail Removed)> wrote in message
news

D1D6F87-C271-4434-A44C-(E-Mail Removed)...
> Hi.
>
> I have an application that uses V2 framework. A Windows form application
> calls a COM+ component function using HTTP remoting (binary channel). ie:
>
> ChannelServices.RegisterChannel(New HttpChannel(Nothing, New
> BinaryClientFormatterSinkProvider, Nothing), False)
>
> The COM+ function queries a database and returns a dataset with its
> RemotingFormat property set to binary ie:
>
> ds.RemotingFormat = SerializationFormat.Binary.
>
> When the front-end receives the dataset and I check the RemotingFormat it
> indicates XML!!!
>
> Does binary dataset serialization work over HTTP remoting? Is this a bug?
>
> Thanks, Mark