title: Does the machine configuration affect the accessibility of serialized output created using protobuf-net?
body: <p>I am using protobuf-net to encrypt, serialize and store the contents of an object into a file and am using contents of the file after decrypting and desiralizing into the original object.</p>
  
  <p>The object can be decrypted, and deserialized perfectly through my application on the machine on which it was created but when the exact same application reads the exact same file when executed on another machine, it throws an exception asking me to refer to one of the existing questions on stackoverflow. I am unable to post the exact stacktrace right now but will be doing so shortly.</p>
  
  <p>My question is - does the physical configuration of the machine on which the serialization and storage of an object into a file takes place have any bearing on its availability elsewhere?</p>
  
  <p>I think this should not be the case as it would defeat the purpose of serialization and that there is a gap in my understanding.</p>
  
  <p>All help is sincerely appreciated.</p>
  
  <p>Thanks!</p>
  
  <p><strong>EDIT:</strong></p>
  
  <p>Thanks Marc! - for both the reply and the awesome library itself. I'll post back more details regarding the stack trace, the encryption technique used, and the length and bytes of the contents. Though I doubt that there is a problem in the encryption/decryption code logic since the same code creates and uses the file successfully on one machine. Overwriting an existing file can also be ruled out as the created files are named using a guid so the name  getting repeated is improbable. Could you please clarify on what exactly you mean by "by treating the file as text at some point"?  </p>