[ADVANCED-DOTNET] ANNOUNCE: Come one, come all to our new " Longhorn" listserv

2003-10-29 Thread Jason Whittington
Hi everyone, I think the subject says it all - DevelopMentor and I have just launched [EMAIL PROTECTED] Come on over and join us to discuss all the new stuff in the "Longhorn" platform. Pretty much anything related to "Longhorn" will be fair game, including: * WinFS * Avalon and WinFX * Next Ge

[ADVANCED-DOTNET] out of memory when deserializing

2003-10-29 Thread Craig Cody
Here's the scenario - The client requests lots of data. The request passes through the middle tier to the database. The data returns through the middle tier back to the client. The Mb's of data get to the client where it is deserialized into objects. When attempted on the 1.0 framework, no pro

Re: [ADVANCED-DOTNET] Serialization Problem

2003-10-29 Thread Andrew Gayter
It looks like you're either not serializing it correctly, or you're deserializing on a different machine? Change to a SOAP/XML formatter and dump the received stream to a file, or debug - check it out and make sure it's okay. > -Original Message- > From: Moderated discussion of advanced .

Re: [ADVANCED-DOTNET] Serialization Problem

2003-10-29 Thread Akshay Arora
> I am using socket programming and not remoting. I am creating the > application on a stand alone machine having only one version of .NET > framework. > How can i resolve this error? I actually do the same thing, but I use XML Serialization. The code should be the same. What is the code you use t

Re: [ADVANCED-DOTNET] Serialization Problem

2003-10-29 Thread Ed Stegman
Serialize your object to a byte array. Send the client an int containing the length of the byte array, followed by the byte array. The client reads the int from the network stream, and then reads number of bytes specified by the int into a byte array. DeSerialize the byte array into an object and a

Re: [ADVANCED-DOTNET] Serialization Problem

2003-10-29 Thread Frans Bouma
> I am serializing an object and sending it through > networkstream to another computer. However when i try to > deserialize it, it is giving me a error "BinaryFormatter > Version incompatibility. Expected Version 1.0 Recieved > version 1566270836.0" > > I am using socket programming and not r

Re: [ADVANCED-DOTNET] Serialization Problem

2003-10-29 Thread Thomas Tomiczek
By fixing your programming error. At some point in the serialization/eserialization/transfer process you seem to loose/chagne/gargabe the data. That simple. Sorry if this is not helpful, but with the innformation given this is the only hadvice I can give you. Serialization DOES work, so you must

[ADVANCED-DOTNET] Serialization Problem

2003-10-29 Thread dotnetminer
I am serializing an object and sending it through networkstream to another computer. However when i try to deserialize it, it is giving me a error "BinaryFormatter Version incompatibility. Expected Version 1.0 Recieved version 1566270836.0" I am using socket programming and not remoting. I am crea