[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 334
  • Last Modified:

C# ->> Memcache and deserialisation

Hi,

I have a little C# application that successfully collects a value from memcache, it then attemptss to deserialise what I have using a memoryStream and BinaryFormatter.

Here is the code...

using (MemcachedClient writeClient = new MemcachedClient())
            {                
                string frObj= writeClient.Get<string>("myser");                
                byte[] byteArray = Encoding.ASCII.GetBytes(frObj);
                MemoryStream stream = new MemoryStream(byteArray);
                stream.Position = 0;
                BinaryFormatter bf = new BinaryFormatter();
                object d = bf.Deserialize(stream);
            }

Open in new window


I can get at the data and retrieve it. I just cant deserialise it into an object. The follow line gives me a SerialisationException was unhandled runtime.
 object d = bf.Deserialize(stream);

Open in new window


It states the following.
End of Stream encountered before parsing was completed.

I was wondering if anyone can help me to resolve this and prevent this runtime error or at least handle it.

Thank you.
Regards,
0
meetsys
Asked:
meetsys
  • 4
  • 4
1 Solution
 
käµfm³d 👽Commented:
Deserialize the byte array that the MemoryStream holds, not the MemoryStream itself. In other words, change line 8 to:

 object d = bf.Deserialize(stream.ToArray());

Open in new window

0
 
meetsysAuthor Commented:
That just gives off more runtime errors.

I get this one...

cannot convert from 'byte[]' to 'System.IO.Stream'

and an invalid arguments. This site is great. I never know about it before. Any ideas where I am going wrong.
0
 
käµfm³d 👽Commented:
What does your serialization code look like?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
meetsysAuthor Commented:
The serialisation code is a string of data that comes from another program. In fact it is actually serialised in .php and then passed to the 3rd party memcache and then picked up in c#. I'm just trying to deserialise it, not worried if it comes out wrong. Even if its not the same as how it went in. Just want to have something output.
0
 
käµfm³d 👽Commented:
If we're talking about the same PHP code that you demonstrated in your previous question, then I don't see where there is any serialization going on. Even if there were, you are talking about serialization/deserialization between two different programming languages. If you truly are serializing in your PHP code, then you need to use a form of serialization that is more cross-platform, like XML or JSON.
0
 
meetsysAuthor Commented:
Sure I get it. But it should still do something. Some sort of process that doesn't involve the runtime error I was enquiring about. Thats all I am looking to resolve at present.
0
 
käµfm³d 👽Commented:
OK, then if I am correct in that you are not serializing in the PHP, then simply remove the BinaryFormatter business.

i.e.

using (MemcachedClient writeClient = new MemcachedClient())
{                
    string frObj = writeClient.Get<string>("myser");
}

Open in new window


Since it's a string that you put into memcached, that should be what you are getting back. No need to deserialize anything. Had you put something more involved into memcached--say a JSON object--then deserailization may come into play.
0
 
meetsysAuthor Commented:
Thanks for all your advise kaufmed. Really appreciate it. Tricky business, some of this serialisation, memcache stuff. Thanks
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now