title: NetDataContractSerializer and assembly versions mismatch
body: <p>I'm using <strong><em>NetDataContractSerializer</em></strong> to exchange data among applications. I would like the <strong><em>ReadObject</em></strong> method throw an exception when assembly versions don't match.</p>
  
  <p>Now, for example, when I serialized my object from assembly version 1.0.0.0 and later deserialize it having same assembly but now version 1.0.0.1, the <strong><em>NetDataContractSerializer</em></strong> happily swallows the stream and deserializes without problems. </p>
  
  <p>Is it possible to abort the deserialization process when versions don't match?</p>
  
  <p>UPDATE: I need version intolerance because of many reasons. This is both a requirement from a customer, as well as a requirement to be absolutely certain that import processes the file that was exported from the same version of the application. In case of my application, changing version makes useless the previous import process, because version change equals to more or less involved internal structure change.</p>