DataSet Serialization Not Working with VS.NET Beta2

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jed - 29 Apr 2005 17:30 GMT

I am testing WSE 2.0 sp3 with the new VS.NET 2005 Beta2 bits and am having
problems passing DataSet objects. This acts just like the problem that WSE
2.0 had upon initial release, which is some sort of DataSet serialization
issue. Simple types pass ok.

Anyone else seeing this problem?

If this truly is a problem, I really don't understand why the WSE 2 Team and
the VS.NET 2005 Team can't work more closely together. I understand from
posting this problem on the VSTS General newsgroup that an
"under-development" WSE 3.0 release will be fully integrated with
2005--cool--but some of us that have been *seriously* using WSE 2.0 since its
initial release have continually been left holding the bag when trying to
prepare for the VS.NET 2005/Framework 2.0 release. (Please forgive the rant
if somehow I'm all washed up on the DataSet issue.)

If this truly turns out to be an issue, it would be really *swell* to have a
WSE 2.0 fix posted as soon as possible.

Thank you in advance!

Reply to this Message

Mike - 29 Apr 2005 18:23 GMT

It was stated in an MSDN event yesterday that WSE 2.0 is NOT compatible with
VS 2005. Bummed me out cause I am getting ready to start a major project
with 2005 and we use WS-Security extensively.

>I am testing WSE 2.0 sp3 with the new VS.NET 2005 Beta2 bits and am having
> problems passing DataSet objects. This acts just like the problem that
[quoted text clipped - 21 lines]
>
> Thank you in advance!

Reply to this Message

William Stacey [MVP] - 13 May 2005 17:24 GMT

Until the FX fix(es), you could just create your own table/row/column
objects using generic collections. A bit more work, but kinda fun with
generics and on the plus side, may offer a bit more flex. So you could
serialize your table/dataset as normal. If you wanted datatable on the
client side for binding, you could then create a datatables using your
objects. You can bind to collection<T> collections, I think, as it
inherites from bindinglist. Naturally this is a bit more work and would not
give you things like relationships.

Signature

William Stacey [MVP]

Reply to this Message

Sami Vaaraniemi - 13 May 2005 18:48 GMT

One way to work around this issue would be to use an XmlDataDocument for
serializing the DataSet. I've been using that for a while with typed
DataSets. This gives me the best of both worlds: simple and interoperable
XML on the wire, and convenient typed DataSets in the consumer and on the
business logic layer.

Regards,
Sami

> Until the FX fix(es), you could just create your own table/row/column
> objects using generic collections. A bit more work, but kinda fun with
[quoted text clipped - 30 lines]
>>
>> Thank you in advance!

Reply to this Message

DataSet Serialization Not Working with VS.NET Beta2

Free Magazines