stability .net serialization opposing opposite horizon versions


a digest i'm operative requires serializing information structure before shutting down restores the state serialized information start adult again.



last year, building .net 1.1, ran machiavellian emanate where




  • our formula ran .net 2.0

  • a fan upgraded program somehow set 1.1 default

  • our formula ran .net 1.1 amateurish deserialize the stored state



this sole emanate "resolved" proud sole program upgrade, shouldn't problem we're targeting .net 2.0 horizon (so can't presumably run 1.1).



what luck serialization again change incompatibly between, 2.0 newer frameworks? <supportedversion> repair the formula 2.0.50727, chances changes between 2.0.50727.1434 2.0.50727.nnnn (some destiny release)? information structures being serialized arrays, maps, strings, et cetera customary category libraries.



additionally, guaranteed 2.0.50727 horizon always hallowed even after offer .net upgrades? pointers microsoft support welcome.



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members