Problems With BinaryFormatter
-
I'm using BinaryFormatter to serialize/deserialize some of my custom classes. On my development PC, everything is working fine but this morning, I installed the app on another PC and tried to load (deserialize) one the files. The object is deserialized with no errors but the string field: "ContactName" is null! Keep in mind that my development PC loads the file perfectly and I manually copied the same .exe and all Dlls from the dev PC to the other PC. Here's the code sample: // //Deserialization... // BinaryFormatter bf = new BinaryFormatter(); using (FileStream fs = File.Open(filePath, FileMode.Open)) { _SelectedTemplate = (LabelTemplate)bf.Deserialize(fs); } I'm I going crazy or do I send a nasty comment to Microsoft?
If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.
-
I'm using BinaryFormatter to serialize/deserialize some of my custom classes. On my development PC, everything is working fine but this morning, I installed the app on another PC and tried to load (deserialize) one the files. The object is deserialized with no errors but the string field: "ContactName" is null! Keep in mind that my development PC loads the file perfectly and I manually copied the same .exe and all Dlls from the dev PC to the other PC. Here's the code sample: // //Deserialization... // BinaryFormatter bf = new BinaryFormatter(); using (FileStream fs = File.Open(filePath, FileMode.Open)) { _SelectedTemplate = (LabelTemplate)bf.Deserialize(fs); } I'm I going crazy or do I send a nasty comment to Microsoft?
If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.
Richard Blythe wrote:
Keep in mind that my development PC loads the file perfectly and I manually copied the same .exe and all Dlls from the dev PC to the other PC.
And what about the data file, is that the same on both PC? Keep in mind thousands of developer (including me!) used serialization without a hitch for a long while! ;)
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
-
I'm using BinaryFormatter to serialize/deserialize some of my custom classes. On my development PC, everything is working fine but this morning, I installed the app on another PC and tried to load (deserialize) one the files. The object is deserialized with no errors but the string field: "ContactName" is null! Keep in mind that my development PC loads the file perfectly and I manually copied the same .exe and all Dlls from the dev PC to the other PC. Here's the code sample: // //Deserialization... // BinaryFormatter bf = new BinaryFormatter(); using (FileStream fs = File.Open(filePath, FileMode.Open)) { _SelectedTemplate = (LabelTemplate)bf.Deserialize(fs); } I'm I going crazy or do I send a nasty comment to Microsoft?
If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.
You're not going crazy; .NET serialization is full of bugs. Things don't work as advertised, and you have to come up with time-consuming workarounds. This is an example of what I call a "black-box failure", when a component you depend on, that you don't have the source code for malfunctions. It can be devastating, since you can't fix it. The standard approach to a black-box failure is to try to find a different way of doing the same thing. Another tactic is to upgrade to a later version of .NET, where the bug may have been fixed.